About
JDBC Driver Manager Trace
You can use the JDBC Driver Manager Trace tool to trace a
connection to any database that you access in PowerBuilder through the
JDBC interface.
Unlike the Database Trace tool, the JDBC Driver Manager Trace tool
cannot trace connections through one of the native database
interfaces.
What this tool does
JDBC Driver Manager Trace logs errors and informational messages
originating from the Driver object currently loaded (such as SAP’s
jConnect JDBC driver) when PowerBuilder connects to a database through
the JDBC interface. It writes this information to a default log file
named JDBC.LOG or to a log file that you specify. The amount of trace
output varies depending on the JDBC driver being used.
What both tools do
The information from JDBC Driver Manager Trace, like Database
Trace, can help you:
-
Understand what PowerBuilder is doing internally while
connected to a database through the JDBC interface -
Identify and resolve problems with your JDBC connection
-
Provide useful information to Technical Support if you call
them for help with your database connection
When to use this tool
Use JDBC Driver Manager Trace instead of the Database Trace tool
if you want more detailed information about the JDBC driver.
Performance considerations
Turning on JDBC Driver Manager Trace can slow your performance
while working in PowerBuilder. Therefore, use JDBC Driver Manager
Trace for debugging purposes only and keep it turned off when you are
not debugging.
JDBC.LOG file
PowerBuilder writes JDBC Driver Manager Trace output to a default
log file named JDBC.LOG or to a log file that you specify. The default
location of JDBC.LOG is a temp directory.