Any available supporting data such as SQLCA data structures, and pointers 

to the location of any extra dump or trap files

Administrative events, i.e. backup/restore start and finish

Example 9 8 contains an extract of a db2diag.log taken at 

DIAGLEVEL

 3.

Example 9 8   Example of db2diag.log file

(1) 2004 02 10 02.26.33.004000   (2) Instance:DB2INST1   (3) Node:000

(4) PID:1012(db2syscs.exe)   (5) TID:1996   (6) Appid:*LOCAL.DB2.00E049090924

(7) data management  (8) sqldEscalateLocks  (9) Probe:3  (10) Database:DB2_EMP2

(11) ADM5502W  The escalation of "1251" locks on table "DB2INST1  .TABLE01" to 

lock intent "X" was successful.

Explanations of the db2diag.log

entries are included below. The number in 

parenthesis corresponds to the following numbers:

(1) Date and timestamp of the entry made into the log

(2) Name of the instance

(3) Node or partition number

This number is always 0 in a single partition configuration.

(4) Process ID of the application or agent

(5) Thread ID of the application or agent

This is only used on the Windows platform.

(6) The application ID

This corresponds to the 

LIST APPLICATIONS

 command output, each 

application has a unique application ID.

(7) Component name 

(8) Name of the function in the component that is reporting an error or 

information

(9) Probe point in the function

This corresponds to a location in the source code of the function that has 

returned an error or information.

(10) Name of the accessed database that generated the message

(11) Diagnostic information

In this example this is a administration warning telling about lock escalation 

(1251 row locks where successfully replaced by one table lock) on table 

DB2INST1.TABLE01.

280 

MySQL to DB2 UDB Conversion Guide