DB2 - Problembeschreibung
Problem IC77012 | Status: Geschlossen |
"INVALID LOG RECORD TYPE" 008C OR 008D REPORTED DURING PERFORMING TABLESPACE ROLLFORWARD THROUGH F2PC LOG RECORD | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
"Invalid log record type" will be reported if both of following conditions are met. - tablespace rollforward is running, and - F2PC(Federated Two Phase Commit) log record is rolled forward. You may see messages in db2diag.log like below. ---------------------------------------------------------------- -------- 2011-06-13-05.09.50.267160+480 E405880A464 LEVEL: Warning PID : 4247602 TID : 2829 PROC : db2sysc 0 INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.DB2INST1.110612210948 AUTHID : DB2INST1 EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:980 MESSAGE : ADM1602W Rollforward recovery has been initiated. 2011-06-13-05.09.50.269601+480 E406345A507 LEVEL: Info PID : 4247602 TID : 2829 PROC : db2sysc 0 INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.DB2INST1.110612210948 AUTHID : DB2INST1 EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:1820 MESSAGE : ADM1604I DB2 is invoking the forward phase of the table space rollforward recovery. ..... 2011-06-13-05.09.52.416943+480 I408174A541 LEVEL: Severe PID : 4247602 TID : 2829 PROC : db2sysc 0 INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.DB2INST1.110612210948 AUTHID : DB2INST1 EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlprfwdt, probe:11510 MESSAGE : Invalid log record type. Dump follows. DATA #1 : Hexdump, 2 bytes 0x070000000D7F2024 : 008C .. 2011-06-13-05.09.52.417263+480 I408716A178 LEVEL: Severe PID:4247602 TID:2829 NODE:000 Title: SQLP_LRH Dump File:/home/db2inst1/sqllib/db2dump/4247602.2829.000.dump.bin 2011-06-13-05.09.52.609882+480 I408895A606 LEVEL: Error PID : 4247602 TID : 2829 PROC : db2sysc 0 INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.DB2INST1.110612210948 AUTHID : DB2INST1 EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecoveryTblSpace, probe:30 RETCODE : ZRC=0x80100078=-2146434952=SQLP_TRECOVF "Recovery process failed. used by BSU only. Active cursor on drop table" DIA8131C Roll forward recovery failed, LSN was "". 2011-06-13-05.09.52.614244+480 I409502A476 LEVEL: Warning PID : 4247602 TID : 2829 PROC : db2sysc 0 INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.DB2INST1.110612210948 AUTHID : DB2INST1 EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecoveryTblSpace, probe:2000 MESSAGE : Tablespaces left in rollforward-in-progress state. 2011-06-13-05.09.52.614559+480 E409979A475 LEVEL: Warning PID : 4247602 TID : 2829 PROC : db2sysc 0 INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.DB2INST1.110612210948 AUTHID : DB2INST1 EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:8180 MESSAGE : ADM1611W The rollforward recovery phase has been completed. ---------------------------------------------------------------- ----------- The function name sqlpForwardRecoveryTblSpace means rollforward recovery on tablespace. The "Invalid log record type" 008C(or 008D) is a F2PC(Federated 2 Phase Commit) log record type which should be handled by rollforward correctly but failed due to defect. After experiencing this problem, then the tablespace will be placed in the state of rollforward in progress(or combined with other state). | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * "Invalid log record type" will be reported if both of * * following conditions are met. * * - tablespace rollforward is running, and * * - F2PC(Federated Two Phase Commit) log record is rolled * * forward. * * * * You may see messages in db2diag.log like below. * * ------------------------------------------------------------ * * ------------ * * 2011-06-13-05.09.50.267160+480 E405880A464 LEVEL: * * Warning * * PID : 4247602 TID : 2829 PROC : * * db2sysc 0 * * INSTANCE: DB2INST1 NODE : 000 DB : * * SAMPLE * * APPHDL : 0-7 APPID: * * *LOCAL.DB2INST1.110612210948 * * AUTHID : DB2INST1 * * EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 * * FUNCTION: DB2 UDB, data protection services, sqlufrol, * * probe:980 * * MESSAGE : ADM1602W Rollforward recovery has been initiated. * * * * 2011-06-13-05.09.50.269601+480 E406345A507 LEVEL: * * Info * * PID : 4247602 TID : 2829 PROC : * * db2sysc 0 * * INSTANCE: DB2INST1 NODE : 000 DB : * * SAMPLE * * APPHDL : 0-7 APPID: * * *LOCAL.DB2INST1.110612210948 * * AUTHID : DB2INST1 * * EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 * * FUNCTION: DB2 UDB, data protection services, sqlufrol, * * probe:1820 * * MESSAGE : ADM1604I DB2 is invoking the forward phase of the * * table space * * rollforward recovery. * * * * ..... * * * * 2011-06-13-05.09.52.416943+480 I408174A541 LEVEL: * * Severe * * PID : 4247602 TID : 2829 PROC : * * db2sysc 0 * * INSTANCE: DB2INST1 NODE : 000 DB : * * SAMPLE * * APPHDL : 0-7 APPID: * * *LOCAL.DB2INST1.110612210948 * * AUTHID : DB2INST1 * * EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 * * FUNCTION: DB2 UDB, recovery manager, sqlprfwdt, probe:11510 * * MESSAGE : Invalid log record type. Dump follows. * * DATA #1 : Hexdump, 2 bytes * * 0x070000000D7F2024 : 008C * * .. * * * * 2011-06-13-05.09.52.417263+480 I408716A178 LEVEL: * * Severe * * PID:4247602 TID:2829 NODE:000 Title: SQLP_LRH * * Dump * * File:/home/db2inst1/sqllib/db2dump/4247602.2829.000.dump.bin * * * * 2011-06-13-05.09.52.609882+480 I408895A606 LEVEL: * * Error * * PID : 4247602 TID : 2829 PROC : * * db2sysc 0 * * INSTANCE: DB2INST1 NODE : 000 DB : * * SAMPLE * * APPHDL : 0-7 APPID: * * *LOCAL.DB2INST1.110612210948 * * AUTHID : DB2INST1 * * EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 * * FUNCTION: DB2 UDB, recovery manager, * * sqlpForwardRecoveryTblSpace, probe:30 * * RETCODE : ZRC=0x80100078=-2146434952=SQLP_TRECOVF * * "Recovery process failed. used by BSU only. * * Active cursor on drop table" * * DIA8131C Roll forward recovery failed, LSN was "". * * * * 2011-06-13-05.09.52.614244+480 I409502A476 LEVEL: * * Warning * * PID : 4247602 TID : 2829 PROC : * * db2sysc 0 * * INSTANCE: DB2INST1 NODE : 000 DB : * * SAMPLE * * APPHDL : 0-7 APPID: * * *LOCAL.DB2INST1.110612210948 * * AUTHID : DB2INST1 * * EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 * * FUNCTION: DB2 UDB, recovery manager, * * sqlpForwardRecoveryTblSpace, probe:2000 * * MESSAGE : Tablespaces left in rollforward-in-progress state. * * * * 2011-06-13-05.09.52.614559+480 E409979A475 LEVEL: * * Warning * * PID : 4247602 TID : 2829 PROC : * * db2sysc 0 * * INSTANCE: DB2INST1 NODE : 000 DB : * * SAMPLE * * APPHDL : 0-7 APPID: * * *LOCAL.DB2INST1.110612210948 * * AUTHID : DB2INST1 * * EDUID : 2829 EDUNAME: db2agent (SAMPLE) 0 * * FUNCTION: DB2 UDB, data protection services, sqlufrol, * * probe:8180 * * MESSAGE : ADM1611W The rollforward recovery phase has been * * completed. * * ------------------------------------------------------------ * * --------------- * * * * The function name sqlpForwardRecoveryTblSpace means * * rollforward recovery on tablespace. * * The "Invalid log record type" 008C(or 008D) is a * * F2PC(Federated 2 Phase Commit) log record type which should * * be handled by rollforward correctly but failed due to * * defect. * * After experiencing this problem, then the tablespace will be * * placed in the state of rollforward in progress(or combined * * with other state). * **************************************************************** * RECOMMENDATION: * * Update to version 9.1 fixpack 11. * **************************************************************** | |
Local-Fix: | |
To recover the database, please use database restore and rollforward, not use tablespace restore and rollforward. To avoid this problem proactively, you can disable DB2_TWO_PHASE_COMMIT in federated server options, for example, "ALTER SERVER Net8_Server OPTIONS (SET DB2_TWO_PHASE_COMMIT 'N')". | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows | |
Lösung | |
This problem is first fixed in version 9.1 fixpack 11. | |
Workaround | |
To recover the database, please use database restore and rollforward, not use tablespace restore and rollforward. To avoid this problem proactively, you can disable DB2_TWO_PHASE_COMMIT in federated server options, for example, "ALTER SERVER Net8_Server OPTIONS (SET DB2_TWO_PHASE_COMMIT 'N')". | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.06.2011 12.12.2011 12.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.1.FP11 | |
Problem behoben lt. FixList in der Version | |
9.1.0.11 |