DB2 - Problembeschreibung
Problem IC61621 | Status: Geschlossen |
INSERT / UPDATE / DELETE ON USER MAINTAINED MQT IN DPF ENVIRONMENT MAY REPORT BAD PAGE HEADER | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Insert / Update / Delete on user maintained MQT in DPF environment may report Bad Page Header. 2009-01-05-11.27.10.699674-300 I492871600E2618 LEVEL: Severe PID : 4516 TID : 194607311200 PROC : db2sysc 3 INSTANCE: db2inst1 NODE : 003 DB : SAMPLE APPHDL : 1-16555 APPID: *N6.server1.090110232211 AUTHID : USER1 EDUID : 174266 EDUNAME: db2agntp (SAMPLE) 3 FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page, probe:12 MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page Header" DIA8547C An error occurred in a database page header. Checks using db2dart for the tablespace does not report errors. The "Bad Page Header" error is the result of a bad access plan. A signature factor in the access plan would include a Table Queue (TQ) occurring directly after another TQ. For example: 2 BTQ ( 4) 26.6402 1 | 2 DTQ ( 5) 22.1343 1 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * Insert / Update / Delete on user maintained MQT in DPF * * * * environment may report Bad Page Header. * * * * * * * * * * * * 2009-01-05-11.27.10.699674-300 I492871600E2618 LEVEL: * * Severe * * PID : 4516 TID : 194607311200 PROC : * * * * db2sysc 3 * * * * INSTANCE: db2inst1 NODE : 003 DB : * * SAMPLE * * APPHDL : 1-16555 APPID: * * *N6.server1.090110232211 * * AUTHID : USER1 * * * * EDUID : 174266 EDUNAME: db2agntp (SAMPLE) 3 * * * * FUNCTION: DB2 UDB, buffer pool services, sqlb_verify_page, * * * * probe:12 * * * * MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page * * * * Header" * * * * DIA8547C An error occurred in a database page * * header. * * * * * * * * * * * * * * Checks using db2dart for the tablespace does not report * * errors. * * * * * * The "Bad Page Header" error is the result of a bad access * * plan. * * A signature factor in the access plan would include a Table * * * * Queue (TQ) occurring directly after another TQ. * * * * * * * * For example: * * * * * * * * 2 * * * * BTQ * * * * ( 4) * * * * 26.6402 * * * * 1 * * * * | * * * * 2 * * * * DTQ * * * * ( 5) * * * * 22.1343 * * * * 1 * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 Fix Pack 1. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.7 Fix Pack 1. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 20.06.2009 16.12.2009 16.12.2009 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |