DataGrip 2022.2 Help

Cannot find a database object in Database Explorer

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. 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.

  • To synchronize the database state automatically, in the Database Explorer (View | Tool Windows | Database Explorer), click the Data Source Properties button 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 Explorer (View | Tool Windows | Database Explorer) is synchronized with the actual state of the database only when you click the Refresh icon the Refresh button or press Ctrl+F5.

    Refresh the database state

Step 2. Verify that the necessary schemas are selected

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.

No schemas are selected

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 Explorer (View | Tool Windows | Database Explorer). 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.

Default schema
  • To display a schema in the Database Explorer, perform one of the following actions:

    • In the Database Explorer (View | Tool Windows | Database Explorer), right-click a data source and navigate to Tools | Manage Shown Schemas…. 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 Tools | Hide Schemas.

    Show and hide schemas

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 Explorer (View | Tool Windows | Database Explorer), right-click a data source and select Tools | Force Refresh.

    Force refresh schema information

Step 4. Clear and synchronize the schema cache

Step 5. Switch to the JDBC-based introspector

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. Open data source properties. You can open data source properties by using one of the following options:

    • Navigate to File | Data Sources.

    • Press Ctrl+Alt+Shift+S.

    • In the Database Explorer (View | Tool Windows | Database Explorer), 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, DataGrip 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

To report an issue, you can use any option that is described in the Where to report an issue section. But we recommend using the JetBrains Support Center.

Submit a request in the JetBrains Support Center

  1. Open the request form by doing one of the following:

    • Click Help | Contact Support.

      The request form will contain prefilled fields about your product and OS.

    • Go to the Submit a request page.

  2. Fill in the Submit a request form.

    If it is possible, attach some troubleshooting materials.

  3. Click Submit.

Last modified: 14 July 2022