Collections missing from getTables() result with the Connect for JDBC MongoDB Driver

Printable View

Information

Title	Collections missing from getTables() result with the Connect for JDBC MongoDB Driver

URL Name	collections-missing-from-gettables-result-with-the-connect-for-jdbc-mongodb-driver

Article Number	000129303

Environment	Product: Connect for JDBC MongoDB Driver Version: All Supported O/S: All Supported Database: MongoDB Application: N/A

Question/Problem Description

While a full list of the collections can be seen using the mongo command line, the results from calling connection.getMetaData().getTables(null, null, null, null) with the Connect for JDBC MongoDB driver show a list which is missing some or all collections.

Databases missing from meta data results.

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

The driver manages an internal set of local files used for mapping to objects on MongoDB. If these files become corrupt or missing, results may be invalid or unstable.

Resolution

Refresh the local files in one of the following ways:

NOTE: The internal files share the same directory as the schema map's configuration file. This directory is specified by the value you enter for the SchemaMap connection property.

Delete the local files and connect while CreateDB=notExist
Use the SQL extensions Refresh Map or Reload Map. Refresh Map runs a discovery against your native data and updates your internal files accordingly, while Reload Map refreshes the internal files to integrate configuration changes without running a discovery.
Refresh the internal files by launching the DataDirect Schema Tool and opening the corresponding schema map configuration file. When an existing schema is opened with the Schema Tool, the Schema Tool automatically compares the content of the schema configuration file to a snapshot of the data on the wire. When new native objects are detected, the Schema Tool displays the newly detected objects by highlighting them in a hierarchical view of the native data.

Please refer to the Connect for JDBC MongoDB Driver documentation for more details.

Workaround

Notes

Last Modified Date	7/29/2019 6:54 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.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Sitefinity

NativeChat

Kendo UI

Telerik

Test Studio

Fiddler Everywhere

Chef

MOVEitNew Release

WS_FTP

OpenEdge

Kinvey

WhatsUp Gold

DataDirect

Corticon

Kemp

Flowmon

Collections missing from getTables() result with the Connect for JDBC MongoDB Driver

Information

MOVEit
New Release