Notify files

DB2 UDB also provides diagnosis information to the administration notification 

log in case of a failure. On Linux and UNIX platforms, the administration 

notification log is a text file called 

.nfy

, where 

 is the name 

of the instance. It is located in the same directory as the db2diag.log file. On 

Windows, all administration notification messages are written to the Event Log.

The DBM configuration parameter 

NOTIFYLEVEL

 specifies the level of information 

to be recorded:

0   No administration notification messages captured (not recommended)

1   Fatal or unrecoverable errors

2   Immediate action required

3   Important information, no immediate action required (default)

4   Informational messages

Not only DB2 UDB can write to the notify logs, but also the Health Monitor, the 

C

apture and Apply programs, and user applications using the 

db2AdminMsgWrite

API function.

Trap files

Whenever a DB2 UDB process receives a signal or exception (raised by the 

operating system as a result of a system event) that is recognized by the DB2 

signal handler, a trap file is generated in the DB2 diagnostic directory. The files 

are created using the following naming convention:

Linux and UNIX:

  tpppppp.nnn

pppppp

: The process ID (PID)

nnn

: The node where the trap occurred

  Example: t123456.000

Windows:

  DBpppttt.TRP

ppp

 : The process ID (PID)

ttt

 : The thread ID (TID)

  Example: DB123654.TRP

Depending on the signal received or the exception raised, the existence of these 

files can indicate different extremes of consequences. These consequences can 

range from the generation of a simple stack trace back for additional diagnostics, 

 Chapter 9. Testing and tuning 

281