Databases write severe error and warning conditions to the local error log (syslog). Typically, databases also write errors to a database log file, such as the db2diag.log file on DB2.
You can open the db2diag.log file in a text editor.
The example below 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:
ps -fu 46827
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
an04110_ |