Troubleshooting Guide

Using the Administrative Tools Log

Errors and warnings generated by DB2's graphical administrative tools are logged to an ASCII file. This file contains entries from all of the tools, including the Control Center.

Notes

Administrative Tools Log File Sample

The following sample illustrates an administrative tools log file. Note that each entry is written to the file on a single line. In this example, the entries are truncated to fit on the page.
*------------ QDB2/2 SQL03010 Control Center Admin Engine Log Feb 17 09:48:58 1997 (1) ----*
>ERR : (2) 09:49:10 (3) pid=22406 (4) tid=3 (5) [IBM][CLI Driver] SQL1032N  No start (6)
>SEV : 09:49:11 pid=22406 tid=1  Nonzero sqlcode at ..\\admin\aecm.cpp(357) - SQL ERROR ...
*------------ End of Control Center Admin Engine Log Feb 17 09:49:28 1997 (7) ----*
*------------ QDB2/2 SQL03010 Control Center Admin Engine Log Feb 17 09:49:28 1997  -------*
>ERR : 09:50:11 pid=22410 tid=1 SQL Command: select schemaname, owner, remarks from sys...
>ERR : 09:50:11 pid=22410 tid=1 [IBM][CLI Driver][DB2/2] SQL0204N  "SYSCAT.SCHEMATA" ...
>Warn: 09:50:12 pid=22410 tid=1 Nonzero sqlcode at ..\admin\aelist.cpp(2097) - No data ...
*------------ End of Control Center Admin Engine Log Feb 17 11:44:12 1997 -----------*

Legend:

(1)
A line indicating when the tool was started

(2)
The type of message (Informational, Warning, Error, or Severe)

(3)
A timestamp

(4)
The process ID

(5)
The thread ID

(6)
An SQL code and message text (truncated in this example)

(7)
A line indicating when the tool was closed


[ Top of Page | Previous Page | Next Page ]