Ultimate
Cannot find a database object in Database Explorer

Last modified: 29 November 2022

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.

note

If steps 1, 2, and 3 did not resolve your problem, inform JetBrains of your situation by creating a Youtrack ticket. After you have created the ticket, try steps 4 and 5 as a workaround.

Step 1. Refresh 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.

Step 2. Verify that the necessary schemas are selected

note

If you see no schemas in the popup, check whether a connection to a data source is available. Refer to this troubleshooting article or report the situation to us.

When you create a data source, the data source is created with no schemas selected. You need to select schemas with which you plan to work.

The Default schema or Default database is a schema or a database that will be current on connection to a data source. The current schema is a schema that is current in a session. You can change the current schema by using SET CURRENT_SCHEMA. The default schema depends on database settings and data source settings that you set in the JDBC URL.

You can change this default in connection settings of a data source. To change the default, click the Data Source Properties icon The Data Source Properties icon in the Database tool window (View | Tool Windows | Database). In the data sources list, select your data source. In the Database field, type the name of a schema or a database that you want to use as a default.

Step 3. Force refresh schema information

The Force Refresh action clears the data source information from cache and loads it again from scratch.

Step 4. Clear and synchronize the schema cache

Step 5. Switch to the JDBC-based introspector

warning

Switch to the JDBC-based introspector with caution. This step may lead to problems with code generation because some objects and properties become unavailable or return wrong values.

Consider this step as a temporary workaround. If you cannot see objects in the database explorer, you might have a bug. Collect troubleshooting materials and send them to our support team.

Temporary enable introspection with JDBC metadata

  1. In the Database tool window (View | Tool Windows | Database), click the Data Source Properties icon The Data Source Properties icon.

  2. On the Data Sources tab, select the data source that you want to modify.

  3. Click the Advanced tab and select the Introspect using JDBC metadata checkbox.

  4. Synchronize the view (see Step 1. Synchronize the database state).

    Switch to the JDBC-based introspector

Collect information by using Diagnostic tools

To profile the introspection and diagnose possible issues, IntelliJ IDEA can generate three files that include information about the following:

  • dataSource.txt: the data source.

  • introspector.txt: a module that was used to load the metadata from the database.

  • model.xml: a part of the database model.

This information might be helpful when introspection works incorrectly. For example, when you see something outdated or do not see new objects.

Run an introspection profiling

  1. Right-click a data source and navigate to Diagnostics | Prepare Introspector Diagnostics.

  2. Find the three generated files in the file browser window or by clicking their location link in the notification message.

    Notification message with a link to introspection information files

  3. Share the generated files with the support team.

The following screenshot shows the example output of these three files.

Prepare introspector diagnostic