DB2 - Problembeschreibung
Problem IC63981 | Status: Geschlossen |
CRASH RECOVEY FOR DATABASE HAVING INDOUBT TRANSACTION IS FAILING WITH -1042C WHEN ONLINE BACKUP WITH INCLUDE LOGS IS RESTORED | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
This problem occurs when following steps are performed - Start online backup with INCLUDE LOGS - Start a two-phase commit transaction - The online backup with INCLUDE LOGS finishes, but the two-phase commit transaction is not yet complete - Restore the backup to another database, and rollforward to end of logs. When we try to connect to DB after restore and RF crash recovery will fail and we will get SQL1042C error Message in db2diag.log 2008-08-27-14.44.51.913227+120 I16938A455 LEVEL: Warning PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-11 APPID: *LOCAL.db2v91.080827124141 AUTHID : DB2V91 FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:2210 DATA #1 : <preformatted> Invoking database rollforward backward recovery, nextLsn: 000000264189000C 2008-08-27-14.44.53.207366+120 I17394A485 LEVEL: Error PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-11 APPID: *LOCAL.db2v91.080827124141 AUTHID : DB2V91 FUNCTION: DB2 UDB, recovery manager, sqlprbck, probe:1790 MESSAGE : XA indoubt on coordinator node: DATA #1 : Hexdump, 8 bytes 0x07800000EACDFB80 : 0000 0000 38D8 7FDD ....8... 2008-08-27-14.44.53.488780+120 E17880A1366 LEVEL: Severe PID : 1114268 TID : 1 PROC : db2resync INSTANCE: db2v91 NODE : 000 APPHDL : 0-5 FUNCTION: DB2 UDB, base sys utilities, sqleProcessRMentry, probe:40 MESSAGE : DIA6009C RM resync failed on the RM database "DB2P001 ". DATA #1 : XID, PD_XA_TYPE_XID, 140 bytes FormatID: 53514C20 ( SQL ) Gtrid Length: 17 Bqual Length: 10 Data: 4445 4744 464C 422E 4444 464C 5550 3120 20C2 B277 C813 D734 3236 3000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 3 sqlerrmc: 353 sqlerrp : SQLRESYC sqlerrd : (1) 0x80370161 (2) 0x00000161 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2008-08-27-14.44.53.958416+120 E19247A423 LEVEL: Warning PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-11 APPID: *LOCAL.db2v91.080827124141 AUTHID : DB2V91 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:8180 MESSAGE : ADM1611W The rollforward recovery phase has been completed. 2008-08-27-14.44.54.226209+120 I19671A402 LEVEL: Warning PID : 1122368 TID : 1 PROC : db2loggr (VMDBP) INSTANCE: db2v91 NODE : 000 FUNCTION: DB2 UDB, data protection services, sqlpghck, probe:1880 MESSAGE : DIA2030W In-doubt transaction(s) exists at database shutdown time. Crash recovery will be performed on the next database connection. and later when crash recovery is started is shows 2008-08-27-14.46.52.890353+120 I22647A325 LEVEL: Warning PID : 1052830 TID : 1 PROC : db2loggw (VMDBP) INSTANCE: db2v91 NODE : 000 FUNCTION: DB2 UDB, data protection services, sqlpgasn2, probe:2820 DATA #1 : <preformatted> Need to complete the truncation on log extent 18821 2008-08-27-14.46.52.922294+120 I22973A454 LEVEL: Warning PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-12 APPID: *LOCAL.db2v91.080827124609 AUTHID : DB2V91 FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4000 MESSAGE : DIA2051W Forward phase of crash recovery has completed. Next LSN is "000000264189000C". 2008-08-27-14.46.52.923190+120 I23428A397 LEVEL: Severe PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-12 APPID: *LOCAL.db2v91.080827124609 AUTHID : DB2V91 FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4110 MESSAGE : Recovery did not reach the end of the logs! and fails Backup image does not include all the logs which are required by the crash recovery | |
Problem-Zusammenfassung: | |
Users affected:All ERROR DESCRIPTION: This problem occurs when following steps are performed - Start online backup with INCLUDE LOGS - Start a two-phase commit transaction - The online backup with INCLUDE LOGS finishes, but the two-phase commit transaction is not yet complete - Restore the backup to another database, and rollforward to end of logs. When we try to connect to DB after restore and RF crash recovery will fail and we will get SQL1042C error Message in db2diag.log 2008-08-27-14.44.51.913227+120 I16938A455 LEVEL: Warning PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-11 APPID: *LOCAL.db2v91.080827124141 AUTHID : DB2V91 FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:2210 DATA #1 : <preformatted> Invoking database rollforward backward recovery, nextLsn: 000000264189000C 2008-08-27-14.44.53.207366+120 I17394A485 LEVEL: Error PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-11 APPID: *LOCAL.db2v91.080827124141 AUTHID : DB2V91 FUNCTION: DB2 UDB, recovery manager, sqlprbck, probe:1790 MESSAGE : XA indoubt on coordinator node: DATA #1 : Hexdump, 8 bytes 0x07800000EACDFB80 : 0000 0000 38D8 7FDD ....8... 2008-08-27-14.44.53.488780+120 E17880A1366 LEVEL: Severe PID : 1114268 TID : 1 PROC : db2resync INSTANCE: db2v91 NODE : 000 APPHDL : 0-5 FUNCTION: DB2 UDB, base sys utilities, sqleProcessRMentry, probe:40 MESSAGE : DIA6009C RM resync failed on the RM database "DB2P001 ". DATA #1 : XID, PD_XA_TYPE_XID, 140 bytes FormatID: 53514C20 ( SQL ) Gtrid Length: 17 Bqual Length: 10 Data: 4445 4744 464C 422E 4444 464C 5550 3120 20C2 B277 C813 D734 3236 3000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 3 sqlerrmc: 353 sqlerrp : SQLRESYC sqlerrd : (1) 0x80370161 (2) 0x00000161 (3) 0x00000000 (4) 0x00000000 (5) 0x00000000 (6) 0x00000000 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: 2008-08-27-14.44.53.958416+120 E19247A423 LEVEL: Warning PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-11 APPID: *LOCAL.db2v91.080827124141 AUTHID : DB2V91 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:8180 MESSAGE : ADM1611W The rollforward recovery phase has been completed. 2008-08-27-14.44.54.226209+120 I19671A402 LEVEL: Warning PID : 1122368 TID : 1 PROC : db2loggr (VMDBP) INSTANCE: db2v91 NODE : 000 FUNCTION: DB2 UDB, data protection services, sqlpghck, probe:1880 MESSAGE : DIA2030W In-doubt transaction(s) exists at database shutdown time. Crash recovery will be performed on the next database connection. and later when crash recovery is started is shows 2008-08-27-14.46.52.890353+120 I22647A325 LEVEL: Warning PID : 1052830 TID : 1 PROC : db2loggw (VMDBP) INSTANCE: db2v91 NODE : 000 FUNCTION: DB2 UDB, data protection services, sqlpgasn2, probe:2820 DATA #1 : <preformatted> Need to complete the truncation on log extent 18821 2008-08-27-14.46.52.922294+120 I22973A454 LEVEL: Warning PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-12 APPID: *LOCAL.db2v91.080827124609 AUTHID : DB2V91 FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4000 MESSAGE : DIA2051W Forward phase of crash recovery has completed. Next LSN is "000000264189000C". 2008-08-27-14.46.52.923190+120 I23428A397 LEVEL: Severe PID : 1593440 TID : 1 PROC : db2agent (VMDBP) INSTANCE: db2v91 NODE : 000 DB : VMDBP APPHDL : 0-12 APPID: *LOCAL.db2v91.080827124609 AUTHID : DB2V91 FUNCTION: DB2 UDB, recovery manager, sqlprecm, probe:4110 MESSAGE : Recovery did not reach the end of the logs! and fails Backup image does not include all the logs which are required by the crash recovery LOCAL FIX: Ship log file to active directory which is requested by crash recovery and hence Connect to database completes successfully | |
Local-Fix: | |
Ship log file to active directory which is requested by crash recovery and hence Connect to database completes successfully | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in v97 fp1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.10.2009 17.12.2009 17.12.2009 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |