Database logs

You can open the db2diag.log file in a text editor.

The following example shows a typical entry from the db2diag.log file:

Jun 18 15:02:53 bluj DB2[46827]: DB2(db2inst1.000(1))oper_system_services sqlobeep(2)
 reports:(3) 
Jun 18 15:02:53 (4) bluj (5) DB2[46827(6)]: extra symptom string provided:(7) RIDS/sqlesysc_ 
Jun 18 15:02:53 bluj DB2[46827]:     data: (8)  54686973  20697320  616e2065  78616d70         
Jun 18 15:02:53 bluj DB2[46827]:     data:   6c65206f  66206c6f  67676564  20646174          
Jun 18 15:02:53 bluj DB2[46827]:     data:   61                                              
Jun 18 15:02:53 bluj DB2[46827]: 2 piece(s) of dump data provided... to file(9) /u/db2inst1/
Jun 18 15:02:53 bluj DB2[46827]:         1. 'DUMP EXAMPLE #1' has been dumped (10)
Jun 18 15:02:53 bluj DB2[46827]:         2. 'DUMP EXAMPLE #2' has been dumped

The bold numbers in the example show various items in the log file:

(1)

The instance name and node number

(2)

The reporting component and function

(3)

The probe ID and error and alert numbers

(4)

A time stamp for when the event occurred

(5)

The host name

(6)

The process ID of the reporting process. Use the ps command to view information about the process ID of the reporting process. For example, enter the following command to get information about the reporting process:

 ps -fu 46827

(7)

A symptom string that contains additional information about where and why the problem occurred

(8)

A hexadecimal dump of data that includes return codes and other information that can be interpreted by your IBM® Support Center

(9)

Information about additional dump files. Larger structures and other binary data might be dumped to additional files. The name of the file is identified in the syslog file

(10)

An entry to identify a piece of dump data