Troubleshooting Guide

Maintaining a Problem History

Maintain a history of reported problems and the actions you took to identify or resolve them. This information may help you isolate later problems and anticipate or avoid others. In particular, you should record the following information related to a problem:

• The problem description, including:
  • The problem symptoms.
  • A list of the DB2 utilities that were running, including RUNSTATS, REORG, LOAD, IMPORT, and others.
  • A complete description of any messages that were received, including SQLCODEs, associated reason codes, or system error codes.
  • Any SQLSTATE received. SQLSTATEs are useful for diagnosing problems, because they are consistent across all platforms. For a list of SQLSTATEs, see the Message Reference.
• What was happening at the time. By recording information such as the following, you can spot patterns should a problem occur again:
  • The actions that led up to the problem
  • Any applications that were running at the time
  • Any SQL statements that were running at the time, including information on whether they were dynamic or static, and Data Definition Language (DDL) or Data Manipulation Language (DML)
• The type of hardware and software running on your system, and their configuration
• The service level installed on each system or partition server (on Enterprise - Extended Edition systems), and any fix packs applied
• The results of any corrective actions
• The problem resolution
• The number assigned to the problem, if you contacted DB2 Customer Support.