17.1.3 HADB ODBC driver trace information

HADB ODBC driver trace information is output by the trace output functionality (HADB ODBC driver trace) inherent to the HADB ODBC driver. This functionality outputs information about I/O activity between the driver manager and the HADB ODBC driver.

For details about how to acquire HADB ODBC driver trace information, see 17.3 Settings for outputting HADB ODBC driver trace information. For details about the information that is output, see 17.4 Information output as HADB ODBC driver trace information.

▪ Output destination of HADB ODBC driver trace information

HADB ODBC driver trace information is output to one of the following folders:

The folder specified in Trace Directory Path in the Trace Setup dialog box of the ODBC Data Source Administrator
The folder specified in the ADBODBTRCPATH environment variable

The file name of an HADB ODBC driver trace file is as follows:

adbodbtrace_PID_TID_01.log
adbodbtrace_PID_TID_02.log

PID is the process ID of the application or BI tool that uses the HADB ODBC driver expressed as a hexadecimal. TID is the thread ID of the thread started by the process of the application or BI tool that uses the HADB ODBC driver expressed as a hexadecimal.

An HADB ODBC driver trace file is output for each thread of each process that uses the HADB ODBC driver. This means that the number of output files increases in proportion to the number of processes and threads of the applications and BI tools that use the HADB ODBC driver.

The output destination for the trace information switches between adbodbtrace_PID_TID_01.log and adbodbtrace_PID_TID_02.log as each HADB ODBC driver trace file reaches its maximum size. When switching the output destination from one file to the other, if the new destination file has reached its maximum size, the entire contents of the file are deleted before the output of HADB ODBC driver trace information resumes.

Important: HADB opens and closes the HADB ODBC driver trace file each time it outputs HADB ODBC driver trace information. This is likely to significantly impact processing performance. For this reason, we recommend that you do not leave the output of HADB ODBC driver trace information permanently enabled.

To Page Top