Feedback
Did this article resolve your question/issue?

   

Article

Connection attempts to MongoDB return "invalid schema name."

Information

 
TitleConnection attempts to MongoDB return "invalid schema name."
URL NameConnection-attempts-to-MongoDB-return-invalid-schema-name
Article Number000177819
EnvironmentProduct: Connect for JDBC MongoDB driver
Version: 5.1 & 6.0
OS: All supported platforms
Database: Mongo DB
Application: All supported applications
Question/Problem Description
Connection attempts to MongoDB return "invalid schema  name."
Steps to Reproduce
Clarifying Information
The parameters for "Schema Definition" and "Database" have been verified to be correct.
Error Message
Defect Number
Enhancement Number
Cause
The local schema files are not up to date.
Resolution
Regenerate the local schema files to resolve the issue.

Refer to the MongoDB JDBC Driver User's Guide and Reference for details on regenerating local schema files.
Workaround
Notes
References to other documentation:
Progress® DataDirect for JDBC for MongoDB User's Guide, Configuring and connecting : Refreshing the relational map
https://docs.progress.com/bundle/datadirect-mongodb-jdbc-61/page/Refreshing-the-relational-map.html
Last Modified Date6/29/2023 8:15 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.