Collecting data for RDS problems

To analyze a Db2 RDS problem, IBM® Support might request several types of data.

Begin program-specific programming interface information.

In a situation with both a good and bad scenario, include data from both.

When the data is requested as hardcopy, print the data on paper. When the data is requested as softcopy, put the data on a cartridge or tape. For the DDL and DML the preferred format is fixed block, LRECL 80 or 132.

Class 1 data - always needed

A complete copy of the problem query: It is important that this information is an exact, unmodified copy of the query that is causing the problem. If there are host variables in the query, they should be left in the query. Include a hardcopy and a softcopy.
Values that are used for any host variables in the query: Include a hardcopy.
Service SQL documentation for the query: The service SQL documentation includes DDL statements for relevant objects, EXPLAIN records for the SQL statement, and relevant catalog statistics in a standard format for analysis by IBM software support. For instructions, see Collecting service SQL documentation.
Buffer pool sizes (specified in IFCID 0202): Include a hardcopy.
CPU model: Include a hardcopy.
A count of the number of rows that are returned from the query: Include a hardcopy.
DBRMs for static applications: Include a softcopy.

Class 2 data - might be needed

Performance summary report. The preferred report is the Db2 PM accounting summary report. However, if Db2 PM is not available, a summary report from a different performance monitor can be used. Include a hardcopy.

Class 3 data - might be needed

A complete, unformatted storage memory dump at a specified module or at the failure point. An IBM support person can provide more details about how to generate a storage memory dump.

Class 4 data - might be needed

Performance trace of the problem query. The following start command is the most common type of trace. An IBM support person might ask that different trace classes be turned on.

 -START TRACE(PERFM) CLASS(1,2,3,6,8,9,10,32) IFCID(135,136,186)
  RMID(*) DEST(GTF) TDATA(COR,CPU) AUTHID(AUTHID)
  PLANID(PLANID)

DEST(SMF) can be used. The trace must be unformatted. Include a softcopy.

Class 5 data - might be needed

A DSN1COPY of all table spaces and index spaces that are involved in the query, including DDL for all tables that are defined in the table spaces and all DBID, PSID, and OBID information. Include a softcopy.

End program-specific programming interface information.