You can use a text editor to view the administration notification
log file on the machine where you suspect a problem to have occurred.
The most recent events recorded are the furthest down the file.
Generally, each entry contains the following parts:
- A timestamp
- The location reporting the error. Application identifiers allow
you to match up entries pertaining to an application on the logs of
servers and clients.
- A diagnostic message (usually beginning with "DIA" or "ADM") explaining
the error.
- Any available supporting data, such as SQLCA data structures and
pointers to the location of any extra dump or trap files.
The following example shows the header information for a sample
log entry, with all the parts of the log identified.
Note: Not every log entry will contain all of these parts.
2006-02-15-19.33.37.630000 1 Instance:DB2 2 Node:000 3
PID:940(db2syscs.exe) TID: 660 4 Appid:*LOCAL.DB2.020205091435 5
recovery manager 6 sqlpresr 7 Probe:1 8 Database:SAMPLE 9
ADM1530E 10 Crash recovery has been initiated. 11
- Legend:
- A timestamp for the message.
- The name of the instance generating the message.
- For multi-partition systems, the database partition generating
the message. (In a nonpartitioned database, the value is "000".)
- The process identifier (PID), followed by the name of the process,
followed by the thread identifier (TID) that are responsible for the
generation of the message.
-
Identification of the application for which the process is
working. In this example, the process generating the message is working
on behalf of an application with the ID *LOCAL.DB2.020205091435.
This
value is the same as the appl_id monitor element
data. For detailed information about how to interpret this value,
see the documentation for the appl_id monitor
element.
To identify more about a particular application ID,
either:
- Use the LIST APPLICATIONS command on a DB2® server or LIST DCS
APPLICATIONS on a DB2 Connect™ gateway to view a list of application IDs. From this
list, you can determine information about the client experiencing
the error, such as its node name and its TCP/IP address.
- Use the GET SNAPSHOT FOR APPLICATION command
to view a list of application IDs.
- The DB2 component that is
writing the message. For messages written by user applications using
the db2AdminMsgWrite API, the component will read "User
Application".
- The name of the function that is providing the message. This
function operates within the DB2 component
that is writing the message. For messages written by user applications
using the db2AdminMsgWrite API, the function will
read "User Function".
- Unique internal identifier. This number allows DB2 customer support and development to locate
the point in the DB2 source
code that reported the message.
- The database on which the error occurred.
- When available, a message indicating the error type and number
as a hexadecimal code.
- When available, message text explaining the logged event.
DB2 10.5 for Linux, UNIX, and Windows