Fixing Common Problems
These are fixes for problems that are often reported to support. For problems with connecting to a database, see Fixing Connection Issues.
"Certificate is not trusted" is shown
DbVisualizer connects to servers on the internet, for example when it checks for updates, downloads a driver or sends a support request. If it can't verify the certificate of a server, it shows the Certificate is not trusted dialog. If the dialog can't be shown, you get an error that says "PKIX path building failed" instead.
In many organizations, this happens because a security proxy on the network replaces the certificates of all servers with its own. To stop the dialog from coming back, trust your organization's root certificate instead of each server's certificate. In the dialog, select the certificate at the top of the chain and click Accept. If you are not sure which certificate to trust, ask your IT department. See Accepting untrusted certificates.
On Windows, you can instead let DbVisualizer trust the same certificates as Windows does, which usually include your organization's root certificate. Open Tools → Tool Properties, and in the General category, add the following line in the Specify overridden Java VM Properties here field. Then restart DbVisualizer.
-Djavax.net.ssl.trustStoreType=WINDOWS-ROOT
DbVisualizer doesn't start
The most common cause is a Java VM option that isn't valid, for example two options on the same line in Tool Properties. To start DbVisualizer without your own options:
- In the
.dbvisfolder in your home directory, rename the fileuser.vmoptions, for example touser.vmoptions.bak. - Start DbVisualizer.
- Add the options that you need again in Tools → Tool Properties, one option per line. See Java VM options.
If DbVisualizer still doesn't start, contact support using the contact form on the website, and attach the files in the .dbvis/logs folder in your home directory.
The objects tree or auto completion is out of date
DbVisualizer keeps information about the database objects in a cache. If the objects tree, auto completion or object views don't match the database, for example after changes made in another tool, try the following, in this order, until the problem is gone:
- Right-click the connection in the Databases tab and select Refresh Objects Tree.
- Select File → Clear Cache and select the connection.
- Select File → Clear Cache → Clear All, and click Clear.
- Select File → Clear Cache → Clear All, click Reset, and restart DbVisualizer.
Clearing the cache also helps with other problems that come from outdated information about the database, for example a result that you can't edit although it comes from a single table. See Managing the Metadata Cache.
DbVisualizer is slow or stops responding
If it happens when you work with large results or many tabs, DbVisualizer is probably running low on memory. See Handling Memory Constraints.
Otherwise, make a recording of what DbVisualizer does while it is slow, and send it to support. See Recording a performance problem.