For more information about testing products, go to the IBM Rational Web site at: 

http://www.ibm.com/software/rational

9.4  Troubleshooting

The first step of problem determination is to know what information is available to 

you. Whenever DB2 UDB performs an operation, there is a return code 

associated with that operation. The return code is displayed to the user in the 

form of an informational or error message. These messages are logged into 

diagnostic files depending on the diagnostic level set in the DB2 configuration. In 

this section we discuss the DB2 diagnostic logs, error message interpretation, 

tips that may help with problem determination, troubleshooting, as well as the 

resolutions to some specific problems.

The following actions should be taken when experiencing a DB2 related problem:

Check related messages

Explain error codes

Check documentation

Search through available Internet resources

Review APARs for current FixPak level

Use available tools to narrow the problem

Ask IBM for support

9.4.1  Interpreting DB2 informational messages

Start your investigation from the return code. DB2 UDB provides a return code 

for every operation performed in the form of 

CCCnnnnnS

. The prefix 

CCC

 identifies 

the DB2 UDB component that is returning the message; the 

nnnnn

 is a four or five 

digit number which is also referred to as SQLCODE; and the 

S

 is a severity 

indicator. For example, in 

SQL0289N

, the 

SQL

 identifier represents a message from 

the Database Manager, the SQLCODE is 

0289

, and 

N

 indicates an error 

message. 

Here is the complete list for DB2 UDB error messages to prefix your reference:

SQL: Database Manager messages

DB2: Command Line Processor messages

ASN: Replication messages

CLI: Call Level Interface messages

SQJ: Embedded SQLJ in Java messages

SPM: Synch Point Manager messages

DBI: Installation or configuration messages

DBA: Control Center and Database Administration Utility messages

CCA: Client Configuration Assistant messages

 Chapter 9. Testing and tuning 

277