Creating JDBC Diagnostics¶
This section explains how to create a diagnostic from the database logs generated by a Denodo Monitor that was configured to use JDBC Logging Configuration.
Hint
According to your database provider, you may need to import the JDBC drivers first.
To create a JDBC diagnostic follow these steps:
Log in to the Diagnostic & Monitoring Tool.
In case you are running the Diagnostic & Monitoring Tool of a Denodo Platform and the server you are diagnosing does not exist in the catalog yet, you can create it. As you do not need to monitor the server, you can only enter the name of the server in the form.
Right-click on the server and click Load Diagnostic Info from JDBC….
In the Dialog to create a new JDBC diagnostic, select the database provider from the selector and enter the parameters to connect to the database that stores the Denodo Monitor logs. The following database providers are supported:
IBM DB2 11 or higher.
MySQL 5.
MySQL 8 or higher.
Oracle 19c or higher.
PostgreSQL 12 or higher.
Microsoft SQL Server 2019 or higher, which must use the Microsoft driver.
Once all the parameters are inserted, click Find logs.
Dialog to create a new JDBC diagnostic¶
A selector will appear with all the detected servers that contain logs in the database. To create the diagnostic first you need to select from which server you want to load the logs and then click on Create.
Dialog to create a new JDBC diagnostic when the database contains information about several servers¶
The creation process involves several steps for each Denodo Monitor log table in the database: reading logging dates, creating metadata, caching its data and indexing it. According to some external factors, like your internet connection or latency, creating a diagnostic may be a long process. You can follow the creation progress in the notification area.
Progress notification of a JDBC diagnostic creation¶
If you click on the 
button, a new notification area will open where you
can check the current stage for each individual Denodo Monitor log table.
Notification of a JDBC diagnostic creation with information per database table¶
Note
The Denodo Monitor does not export the VDP server event logs when configured to use JDBC Logging. That implies the Errors tab is disabled.
At the end, a new JDBC diagnostic will be created in the tree area, under the server,
represented with the 
icon.
New JDBC diagnostic node in the tree area¶
Note
The Diagnostic & Monitoring Tool supports partial diagnostics where not all the logs could be loaded into the system. This may happen if the database table only contains a subset of all the logs for the diagnosed server or if the caching failed unexpectedly. If that is the case, those features that rely on missing data will be disabled.
To update a JDBC diagnostic with new data, right-click on the diagnostic and click Edit. The Dialog to update a JDBC diagnostic will open. You can either change the database connection parameters or the server to diagnose. In both cases, you first need to click on Find logs to retrieve all the available servers.
Dialog to update a JDBC diagnostic¶
The Diagnostic & Monitoring Tool of a Denodo Platform stores all its
diagnostic-related metadata in a database of the Virtual DataPort Server of the
same installation. The first time you create a diagnostic, it tries to create this
database with the name diagnostic. If the database already exists, the
Confirmation dialog of the diagnostic database name will
appear, asking for a new database name. Change the database name if you
want and confirm. The Diagnostic & Monitoring Tool will use the database you enter in this
dialog even if it already exists.
Confirmation dialog of the diagnostic database name¶