DataGrip
 
2024.2
Shortcuts: Windows
Get DataGrip
You are viewing the documentation for an earlier version of DataGrip.
  1. Support and troubleshooting
  2. Troubleshooting
  3. Cannot find a database object in Database Explorer

Cannot find a database object in Database Explorer

Last modified: 26 May 2024

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, 3, and 4 did not resolve your problem, inform JetBrains of your situation by creating a YouTrack ticket. After you have created the ticket, try step 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.

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

    Refresh the database state

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. For more information, 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.

No schemas are selected

To select the schemas, do one of the following:

The Default schema or Default database is a schema or a database that will be current in 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). From the list of data sources, 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

Step 3. Verify that the tree filter is off

If the items of the object kind are filtered out from the view, the objects wil be hidden in the Database Explorer.

To make sure the database object is not filtered out from the view, do the following:

  1. In the Database Explorer toolbar, click the View Options icon View Options.

  2. Select the Filter icon Filter.

  3. Navigate to the database object kind and make sure that the checkbox is ticked.

The green dot in the corner of filter icon indicates that the filter is on and some objects are filtered out.

Only views and tables are selected to view in Database Explorer

Step 4. 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 Diagnostics | Force Refresh.

    Force refresh schema information

Step 5. Clear and synchronize the schema cache

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.

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.

Switch to the JDBC-based introspector

warning

Switch to the JDBC-based introspector with caution and when requested by the JetBrains support team. 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.