Chapter 2. DB2 UDB architecture overview 79
2.6.3 DB2 administration notification log
The notification log was introduced in DB2 UDB Version 8 and records a subset
of the events such as error and administration logging recorded in prior DB2
versions of the db2diag.log. This information helps DBAs in problem diagnosis.
The administration notification log can also be accessed from the Control Center
by selecting Tools -> Journal, as shown in Figure 2-13 on page 80.
Note: In UNIX, the administration notification log is a text file called
<instance>.nfy, and it is located in <INSTHOME>/sqllib/db2dump, where
<INSTHOME> is the home directory of the instance owner.
On Windows, the administration notification log is written to the Windows
Event Log.
80 DB2 UDB ESE V8 Performance Guide for High Performance OLTP and BI
Figure 2-13 The DB2 administration notification log
As in the case of the db2diag.log, the level of detailed information recorded in the
administration notification log is determined by the NOTIFYLEVEL database
manager configuration parameter, as shown in Table 2-19 on page 81.
Chapter 2. DB2 UDB architecture overview 81
Table 2-19 Administration notification log NOTIFYLEVEL
NOTIFYLEVEL 4 can provide the following locking-related information:
򐂰 Locked object, lock mode, and application holding the lock.
򐂰 Current dynamic SQL statement or static package name.
򐂰 Detailed deadlock information.
򐂰 All tables for which locks are escalated, including:
Number of locks currently held.
Number of locks needed before escalation is completed.
Table identifier information and table name of each table being escalated.
Number of non-table locks currently held.
The table level lock to be acquired as part of the escalation—usually a
Shared lock “S” or eXclusive “X” lock.
For more details on the administration notification log, refer to DB2 UDB
Administration Guide: Performance, SC09-4821.
0 No administration notification messages captured.
1 Only fatal and unrecoverable error are logged. To recover from
some of these conditions, you may need assistance from DB2
2 Conditions that require immediate attention from the SYSADM or
DBA are logged. If the condition is not resolved, it could lead to a
fatal error. This level captures Health Monitor alarms. These are in
addition to NOTIFYLEVEL 1 messages.
3 (default) Conditions that are non-threatening and do not require immediate
action are logged, but it may indicate a non-optimal system. This
level will capture Health Monitor alarms, warnings, and attentions.
These are in addition to NOTIFYLEVEL 1 and 2 messages.
4 Informational messages as well. These are in addition to
NOTIFYLEVEL 1, 2 and 3 messages.
Important: Specify NOTIFYLEVEL of 2 or higher for the Health Monitor to send
notifications to the appropriate contacts defined in its configuration.
Note: NOTIFYLEVEL 4 should normally be used only in exception monitoring

Get DB2 UDB ESE V8 non-DPF Performance Guide for High Performance OLTP and BI now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.