How a Database Profile Is Loaded
DbVisualizer picks the database profile to use based on the Database Type setting of the database connection. You can also select a profile manually in the Database Profile category in the connection properties: select Manually Choose and select the profile, or select "Generic" Profile. Reconnect after you change the profile.
DbVisualizer looks for database profiles in the folders of the search path, which you set in Tool Properties → General → Database Connection → Database Profile. The default search path is:
${dbvis.prefsdir}/ext/profiles${dbvis.home}/resources/profiles
${dbvis.prefsdir} is the folder of the current workspace, by default the .dbvis folder in your home folder. ${dbvis.home} is the DbVisualizer installation folder.
You can add folders and change their order. DbVisualizer searches the folders in the listed order and uses the first profile file with a matching name. Changes to the search path take effect after you restart DbVisualizer.
When DbVisualizer finds the profile, it loads it, loads the profiles it extends, and merges them.
With Auto Detect selected, DbVisualizer uses a profile that extends the profile for the database type, if there is one in the search path. For example, a profile in ${dbvis.prefsdir}/ext/profiles that extends oracle is used for Oracle connections.
If there is no matching profile, DbVisualizer uses the generic profile. It shows only basic information about the objects in the database, and works with most databases that have a JDBC driver.
A database profile other than the generic one is built for a specific database. If you select, for example, the Oracle profile for a Db2 connection, you get errors.