DB2 - Problembeschreibung
Problem IC82364 | Status: Geschlossen |
ONLINE DATABASE BACKUP MAY FAIL WITH "BAD PAGE HEADER" MESSAGES IN PURESCALE IF DATABASE WAS MIGRATED FROM PRE 9.8 LEVEL | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problembeschreibung: | |
If a database was created in v9.5 and migrated to v9.7 but some pages were not touched in v9.7 then these pages would still have pre-cobra page headers. Once the database is moved to v9.8 SD environment and an online backup is executed the backup will fail to verify page header because it is using the new SQLB_PAGE structure and would get some fields wrong when it sets up a temp object descriptor for sqlb_verify_page. Sample error message: 2012-02-08-10.21.49.445360-300 E64730A444 LEVEL: Info PID : 6815904 TID : 42968 PROC : db2sysc 1 INSTANCE: ud40 NODE : 001 DB : SAMPLE APPHDL : 1-120 APPID: sampleid AUTHID : DB2DBA EDUID : 42968 EDUNAME: db2agent (JPOD) 1 FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1634 MESSAGE : Starting an online db backup. 2012-02-08-10.22.40.329109-300 I65175A2045 LEVEL: Severe PID : 6815904 TID : 44115 PROC : db2sysc 1 INSTANCE: ud40 NODE : 001 DB : SAMPLE APPHDL : 1-120 APPID: sampleid AUTHID : DB2DBA EDUID : 44115 EDUNAME: db2bm.42968.3 (SAMPLE) 1 FUNCTION: DB2 UDB, buffer pool services, sqlbDMSMapAndRead, probe:3110 MESSAGE : ZRC=0x87020036=-2029912010=SQLB_BADHDR "Bad Page Header" DIA8547C An error occurred in a database page header. DATA #1 : Page header, PD_TYPE_SQLB_PAGE_HEAD, 48 bytes pageHead: {tbspSeed:0;obj:65534;type:14} PPNum:7 OPNum:0 begoff: 48 datlen: 4048 pagebinx: 0 revnum: 1280 pagelsn: 0000000000000000 flag: 2 future32: 0 cbits1to31: 0 cbits32to63: 0 DATA #2 : String, 98 bytes A corrupt or partially written page has been read during online backup.Please contact IBM Support. CALLSTCK: [0] 0x0900000004A276EC pdLog@glue678 + 0xD4 [1] 0x09000000052813DC sqlbDMSMapAndRead__FP16SQLB_OBJECT_DESC14SQLB_AS_SCHEMEUsUiP12SQ LB_POOL_CBPllPUiT8T7PcT8P12SQLB_GLOBALS + 0xAFC [2] 0x0900000004D79484 sqlbDMSDirectRead__FP19SQLB_DIRECT_READ_CB + 0x8C [3] 0x090000000491441C sqlbDirectRead__FP19SQLB_DIRECT_READ_CB + 0x40 [4] 0x0900000005138838 sqlbDirectReadBlock__FP19SQLB_DIRECT_READ_CBP14SQLB_pfParIoCbUiP UiT4 + 0x1244 [5] 0x0900000006412988 sqlubReadDMS__FP14SQLU_BUFMAN_CB + 0xAF8 [6] 0x0900000007B86454 sqlubBMProcessData__FP14SQLU_BUFMAN_CB + 0x51C [7] 0x0900000006408844 sqlubbuf__FP8sqeAgent + 0x624 [8] 0x0900000005EE9060 sqleSubCoordProcessRequest__FP8sqeAgent + 0x21C [9] 0x0900000004400D88 RunEDU__8sqeAgentFv + 0x344 [10] 0x0900000004A15CC4 EDUDriver__9sqzEDUObjFv + 0x2E4 [11] 0x0900000004A21924 sqloEDUEntry + 0x2E8 [12] 0x09000000007A1E10 _pthread_body + 0xF0 [13] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.8 Fix Pack 5 * **************************************************************** | |
Local-Fix: | |
Take an offline backup if backup is required. | |
Lösung | |
First fixed in DB2 V9.8 Fix Pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 29.03.2012 17.12.2012 17.12.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.8.FP5 | |
Problem behoben lt. FixList in der Version | |
9.8.0.5 |