Troubleshooting database connections

Some objects are not visible in a database connection

There are several situations that might cause objects in a database to not be visible in the Data Source Explorer, after a connection is made.
Non admin users for DB2® for Linux®, UNIX®, and Windows® v8.1

Although non-admin users can connect successfully to a DB2 for Linux, UNIX, and Windows v8.1 database, the Data Source Explorer will not show database objects unless the user ID has SELECT authority for certain SYS* objects. Specifically, the user ID must have SELECT permissions for SYSCAT* objects.

To work around this issue, the user ID must be granted the appropriate SELECT authority.

Filtering in the New Connection wizard
There are some fields in the New Connection wizard that allow you to filter the objects that are retrieved and displayed in the Data Source Explorer, to simplify the view display and improve performance. For example, for products that support Oracle databases, you can select the database catalog that you want to load. View the connection properties to ensure that these fields are set appropriately.

"JDBC driver class not found" error in New Connection wizard

The workbench product includes the files that make up the JDBC driver class for some default drivers. However, if you are connecting to a database that requires a different driver, you must provide the path to the JDBC driver files that were included with your database server. In the New Connection wizard, click the [...] button next to the JDBC driver field to set the path to the files. Refer to your database server documentation to determine the name and typical install location for these files.


Feedback