Cannot find a database object in the database tree view
If you see no objects below the schema level, cannot find changes in objects, experience broken tables or any other visualization problems, try the following steps to resolve the problem.
Step 1. Synchronize the database state
If someone changed the remote database data or view, the local view of the database might differ from the actual state of the database.
To synchronize the database state automatically, in the Database tool window ( ), click the Data Source Properties button and select the data source that you want to change. On the Options tab, select the Auto sync checkbox.
If the Auto sync checkbox is cleared, the view of the data source in the Database tool window ( ) is synchronized with the actual state of the database only when you click the Synchronize icon or press Ctrl+Alt+Y.
Step 2. Verify that the necessary schemas are selected
You can select what schemas you want to show in the database tree view.
In the Database tool window ( ), right-click a data source and navigate to . Select or clear checkboxes of schemas that you want to enable or disable. Press Enter.
Click the N of N link near the data source name. In the schema selection window, select or clear checkboxes of schemas that you want to enable or disable. Press Enter.
To hide all schemas, navigate to.
Step 3. Force refresh schema information
The Force Refresh action clears the data source information from cache and loads it again from scratch.
In the Database tool window ( ), right-click a data source and select .
Step 4. Clear and synchronize the schema cache
Clear the IntelliJ IDEA schema cache (right-click a data source and select Step 1. Synchronize the database state).). Synchronize the view (see
Step 5. Switch to the JDBC-based introspector
To switch to the JDBC-based introspector, click the Data Source Properties button , select the Options tab, and then select the Introspect using JDBC metadata checkbox. Synchronize the view (see Step 1. Synchronize the database state). Consider this step as a temporary workaround.