10.11.4 Examples of output of SQL trace information and how to interpret the information

When there are multiple connections, SQL trace information for all the connections is output at one time. This subsection explains examples of the SQL trace information that is output and how to interpret the information when there are multiple connections.

Prerequisites

The following SQL statements are executed from multiple connections, and SQL trace information is output for each of the SQL statements.

• SELECT * FROM T2

  This SQL statement is executed using the connection whose connection ID is 1.

  This is referred to in the examples as SQL statement [1].

• INSERT INTO ADBUSER01.T2 VALUES (?,?)

  This SQL statement is executed using the connection whose connection ID is 2.

  This is referred to in the examples as SQL statement [2].

Note

The SQL statement basic information and the SQL statement execution information for one connection and the related information^# are output consecutively. Information about other connections is never output within this set of information. Therefore, you can search for information related to an executed SQL statement by using the con_id, con_num, stmt_hdl, and sql_serial_num values that are output as the SQL statement basic information or the SQL statement execution information.

#

Related information means the information explained in (3) Client-definition information to (10) Access path statistical information in 10.11.2 Information that is output as SQL trace information.

■ Example of output of SQL trace information (part 1)

■ Example of output of SQL trace information (part 2)

■ Example of output of SQL trace information (part 3)

■ Example of output of SQL trace information (part 4)

■ Example of output of SQL trace information (part 5)

■ Example of output of SQL trace information (part 6)

■ Example of output of SQL trace information (part 7)

Note

• The SQL statement execution information might not be output in chronological order of the end times of the SQL statements or calls. However, this information is sorted in chronological order within each connection.

• If the output destination files for SQL trace information are swapped, the related information might be output to a different file from the file for the SQL statement basic information and SQL statement execution information. In such a case, you can locate the corresponding SQL statement basic information and SQL statement execution information in the SQL trace file whose number falls immediately before that of the SQL trace file to which the related information has been output (if the trace file number is the smallest value, the information is the last file number).

To Page Top