Notify files

Trap files

Dump files

Messages files

db2diag.log

The db2diag.log is the most often used file for DB2 problem investigation. You 

can find this file in the DB2 UDB diagnostic directory, defined by the 

DIAGPATH

variable in the database manager configuration. If the 

DIAGPATH

 parameter is not 

set, by default the directory is located at:

Linux and UNIX:

$HOME/sqllib/db2dump

where 

$HOME

 is the DB2 instance owner s home directory.

Windows: 

\

where 

 is the directory where DB2 is installed, and 

<

DB2INSTANCE>

 is the name of DB2 instance.

The database manager configuration parameter 

DIAGLEVEL

 controls how much 

information is logged to the 

db2diag.log

. Valid values can range from 0 to 4:

0   No diagnostic data captured 

1   Severe errors only 

2   All errors 

3   All errors and warnings (default)

4   All errors, warnings and informational messages

Most of the time, the default value is sufficient for problem determination. In some 

cases, especially on development or test systems you can set the parameter to 

4

, 

and collect all informational messages. However, be aware that depending on the 

activity, this may cause performance issues due to the large amount of data 

recorded into the file. Setting 

DIAGLEVEL

 to 

4

 may also make the file very large 

and harder to read.

The information in the

db2diag.log includes: 

A diagnostic message (beginning with 

DIA

) explaining the reason for the error

Application identifiers, which allow matching up error entries with 

corresponding application or DB2 server processes

 Chapter 9. Testing and tuning 

279