Troubleshooting Guide

Maintaining a Problem History

It is highly recommended that you maintain a history of reported problems and the actions you took to identify or resolve them. This information can 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 complete description of any messages that are received, including SQL codes, associated reason codes, or system error codes.
  • Any SQL state received. SQL states are useful for diagnosing problems, because they are consistent across all platforms. For a list of SQL states, 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 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, 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 Service

[ DB2 List of Books | Search the DB2 Books ]