By following these steps, you can effectively enable JDBC debug logging from the client side, enhancing your ability to diagnose and troubleshoot issues related to database connections in the client application- SQuirreL :
(1) Open the SQuirreL application and navigate to "file > Global Preferences."
(2) Within the Global Preferences menu, proceed to the "SQL" section. This is where you'll find specific configurations related to SQL settings, including the option to enable JDBC debug logging.
(3) Scroll down in the "SQL" section, locate the "Debug" settings. Adjust the settings as needed to capture detailed trace logs for connections made by the client application via the JDBC driver. The following options are available:
(a)
No Debug: If checked, no debugging information is output from SQuirreL.
(b) JDBC Debug to Output Stream: If checked, instructs JDBC drivers to write debugging information to the JDBC Debug File. Note that this option may generate extensive output and significantly slow down SQuirreL, depending on the JDBC driver in use.
(c) JDBC Debug to Writer: Similar to the Output Stream option, this instructs JDBC drivers to write debugging information to the JDBC Debug File. Be cautious, as this may also impact performance.
(d)
JDBC Debug File: If JDBC Debug is enabled, this display-only setting indicates the file where debug information will be written. If the file name exceeds the label length, the full name will be displayed in a tooltip.
(4) Logs generated will be in the file location specified in JDBC Debug file. Pass this on to
TIBCO Support as needed, for detailed troubleshooting investigation of any issues encountered with the TDV JDBC driver from SQuirreL.