|
Problem IC74440
|
Status: Geschlossen |
after takeover, rollforward failed with SQL1265N against the tablespace which is in rollforward pending state on new primary |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problembeschreibung: |
The scenario can be summarized as following:
1) tablespace container on standby DB become unavailible.
2) perform some updates in primary db.
3) takeover.
4) recover the tablespace container
5) perform the rollforward against recovered tablespace
The rollforward could fail with SQL1265N against the recovered
tablespace when using the rollforward command like:
$ db2 "rollforward db hadrtest to end of logs and stop
tablespace(tbtest)"
Similar entries could be written to db2diag.log:
2010-10-18-03.26.59.125363-240 I83754A590 LEVEL: Error
PID : 60375882 TID : 10575 PROC : db2sysc
INSTANCE: zxianing NODE : 000 DB :
HADRTEST
APPHDL : 0-1612 APPID:
*LOCAL.zxianing.101018072658
AUTHID : ZXIANING
EDUID : 10575 EDUNAME: db2agent (HADRTEST)
FUNCTION: DB2 UDB, recovery manager, sqlpInitTblRecovery,
probe:23
RETCODE : ZRC=0x86100017=-2045771753=SQLPR_BAD_VER_LOG_EXT
"Log extent file is the incorrect version"
DIA8424C An incorrect version of a log file was
encountered.
2010-10-18-03.26.59.126412-240 I84345A535 LEVEL: Error
PID : 60375882 TID : 10575 PROC : db2sysc
INSTANCE: zxianing NODE : 000 DB :
HADRTEST
APPHDL : 0-1612 APPID:
*LOCAL.zxianing.101018072658
AUTHID : ZXIANING
EDUID : 10575 EDUNAME: db2agent (HADRTEST)
FUNCTION: DB2 UDB, recovery manager, sqlpInitTblRecovery,
probe:1410
MESSAGE : firstExt:<
DATA #1 : Hexdump, 12 bytes
0x0700000005FF3340 : 0000 0000 0000 0000 0000 0000
............ |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* The scenario can be summarized as following: *
* *
* *
* *
* 1) tablespace container on standby DB become unavailible. *
* *
* *
* *
* 2) perform some updates in primary db. *
* *
* *
* *
* 3) takeover. *
* *
* 4) recover the tablespace container *
* *
* 5) perform the rollforward against recovered tablespace *
* *
* *
* *
* The rollforward could fail with SQL1265N against the *
* recovered *
* tablespace when using the rollforward command like: *
* *
* *
* *
* $ db2 "rollforward db hadrtest to end of logs and stop *
* *
* tablespace(tbtest)" *
* *
* *
* *
* Similar entries could be written to db2diag.log: *
* *
* *
* *
* 2010-10-18-03.26.59.125363-240 I83754A590 LEVEL: *
* Error *
* PID : 60375882 TID : 10575 PROC : *
* db2sysc *
* INSTANCE: zxianing NODE : 000 DB : *
* *
* HADRTEST *
* *
* APPHDL : 0-1612 APPID: *
* *
* *LOCAL.zxianing.101018072658 *
* *
* AUTHID : ZXIANING *
* *
* EDUID : 10575 EDUNAME: db2agent (HADRTEST) *
* *
* FUNCTION: DB2 UDB, recovery manager, sqlpInitTblRecovery, *
* *
* probe:23 *
* *
* RETCODE : ZRC=0x86100017=-2045771753=SQLPR_BAD_VER_LOG_EXT *
* *
* "Log extent file is the incorrect version" *
* *
* DIA8424C An incorrect version of a log file was *
* *
* encountered. *
* *
* *
* *
* 2010-10-18-03.26.59.126412-240 I84345A535 LEVEL: *
* Error *
* PID : 60375882 TID : 10575 PROC : *
* db2sysc *
* INSTANCE: zxianing NODE : 000 DB : *
* *
* HADRTEST *
* *
* APPHDL : 0-1612 APPID: *
* *
* *LOCAL.zxianing.101018072658 *
* *
* AUTHID : ZXIANING *
* *
* EDUID : 10575 EDUNAME: db2agent (HADRTEST) *
* *
* FUNCTION: DB2 UDB, recovery manager, sqlpInitTblRecovery, *
* *
* probe:1410 *
* *
* MESSAGE : firstExt:< *
* *
* DATA #1 : Hexdump, 12 bytes *
* *
* 0x0700000005FF3340 : 0000 0000 0000 0000 0000 0000 *
* *
* ............ *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.5 Fix pack 8 *
**************************************************************** |
| Local-Fix: |
Restore the tablespace from db backup image and then perform
rollforward |
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
The fix was included in DB2 V9.5 Fix pack8 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.02.2011
30.06.2011
30.06.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.,
9.5.FP8
|
| Problem behoben lt. FixList in der Version |
| 9.5.0.8
|
 |
