APAR status
Closed as program error.
Error description
If the DB2 server is unexpectedly terminated and the DB2 trap file contains SIGSEGV (Signal #11) on UNIX or exception C0000005 on Windows with the following call function stack, it is because of corrupt table or index statistics: . sqlrg_nodecard::getNodeNumber + 0x0 sqlno_prds_is_NPK_adjust_eligible + 0x680 sqlno_prop_compute_cgs_join_adjust_qun + 0x5a7 sqlno_prop_compute_cgs_join_adjustment + 0x2a5 sqlno_prop_compute_cgs_adjustments + 0xac0 sqlno_prop_compute_ff_adjustments + 0x5a sqlno_plan_begin_opr + 0x316 sqlno_call_sf + 0x77 <...snip...> . The purpose of this APAR is to add resiliency to such scenarios, i.e. return an SQL error instead of causing a DB2 server abend: . SQL0901N The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason "Potential corruption in statistics.".) SQLSTATE=58004 . The db2diag.log will contain a message similar to: . 2008-04-21-13.05.38.915985-240 I220900E621 LEVEL: Severe PID : 1334 TID : 183089958 PROC : db2agent INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-51 APPID: *N0.db2inst1.080421170528 AUTHID : db2inst1 FUNCTION: DB2 UDB, SW- optimizer, sqlno_prds_is_npk_adjust_eligible, probe:220 MESSAGE : Stats corruption found for the following table. DATA #1 : String, 8 bytes DB2INST1 DATA #2 : String, 14 bytes TABLE1 DATA #3 : Dumped object of size 47680 bytes at offset 0, 56 byte /home/db2inst1/sqllib/db2dump/13342701332256.000 . To help DB2 support, upon seeing such symptoms please contact the IBM DB2 UDB service immediately.
Local fix
Gather a fresh set of statistics on the failing table and its indexes. The following is an example RUNSTATS command that collects statistics on the table DB2INST1.TABLE1 and all its indexes: . RUNSTATS ON TABLE DB2INST1.TABLE1 WITH DISTRIBUTION AND DETAILED INDEXES ALL; . The DB2 Version 9.1 Information Center contains further details regarding the RUNSTATS command: . http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/ com.ibm.db2.udb.admin.doc/doc/r0001980.htm
Problem summary
See APAR description.
Problem conclusion
Problem resolved via a duplicate APAR IZ21304 first fixed in DB2 UDB 9.1 FixPak 6.
Temporary fix
see APAR description
Comments
APAR Information
APAR number
IZ21535
Reported component name
DB2 DPF
Reported component ID
5724N7400
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-02
Closed date
2008-12-15
Last modified date
2008-12-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ENG_SQNO
Fix information
Fixed component name
DB2 DPF
Fixed component ID
5724N7400
Applicable component levels
R910 PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
15 December 2008