to a complete DB2 instance shutdown due to a serious internal or external 

problem. 

Dump files

When DB2 determines that internal information needs to be collected, it will often 

create binary dump files in the diagnostic path. These files are generated with 

the following format:

Linux and UNIX:

  pppppp.nnn

 or 

lpppppp.nnn

 (for lock list dump)

pppppp

: The process ID (PID)

nnn

: The node where the problem occurred

  Example: 123456.000

Windows:

  pppttt.nnn 

or 

lpppttt.nnn

 (for lock list dump)

ppp

: The process ID (PID)

ttt

: The thread ID (TID)

nnn

: The node where the problem occurred

  Example: 123654.000

Messages files

Some DB2 UDB utilities like 

BIND

, 

LOAD

, 

EXPORT

 and 

IMPORT

 provide an option to 

dump out a messages file to a user defined location. These files contain useful 

information to report the progress, success, or failure of the utility that was run.

9.4.3  DB2 support information

Identifying what information is typically required to resolve problems is a very 

important step. All the conditions that define the problem are essential when 

reviewing documentation, searching through available Internet resources, or 

contacting DB2 support.

Maintenance version

The

db2level

 utility can be used to check the current version of DB2 UDB. As 

presented in Figure 9 4, the utility returns information about the installed 

maintenance updates (FixPaks), the length of word used by the instance (32 bit 

or 64 bit), the build date, and other code identifiers. It is recommended to 

periodically check if the newest available FixPaks are installed. DB2 

maintenance updates are freely available at: 

ftp://ftp.software.ibm.com/ps/products/db2/fixes

282 

MySQL to DB2 UDB Conversion Guide