DB2 - Problembeschreibung
Problem IC79203 | Status: Geschlossen |
REINTEGRATION OF HADR CAN SUCCEED WHILE PRIMARY AND STANDBY ARE ACTUALLY INCONSISTENT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Normally, if HADR primary and standby are not consistent, reintegration will fail. However, if "db2 activate db dbname" is issued after the previous command "db2 start hadr on db dbname as standby" which fails to start up HADR, HADR reintegration could succeed, and primary and standby get into PEER state. . Now, although "db2pd -hadr" shows that HADR is in PEER state, but data on primary and standby are actually out of sync. Afterwards, transactions on primary can be committed as normal. But standby will fail when replaying certain log record. Following is one possible error from db2diag.log on standby: 2011-10-12-04.46.00.497327-420 I211419E613 LEVEL: Severe PID : 16594 TID : 47278437951808PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-28 APPID: *LOCAL.DB2.111012113926 EDUID : 83 EDUNAME: db2redow (SAMPLE) FUNCTION: DB2 UDB, data management, sqldRedoUpsert, probe:1864 MESSAGE : Free Space does not match during redo! DATA #1 : Hexdump, 26 bytes 0x00002B004DA16A78 : 01A2 0200 0400 0000 0C01 A00D 0100 9200 ................ 0x00002B004DA16A88 : 0000 A40D 0000 0C01 0100 .......... 2011-10-12-04.46.00.497534-420 I212033E498 LEVEL: Severe PID : 16594 TID : 47278437951808PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-28 APPID: *LOCAL.DB2.111012113926 EDUID : 83 EDUNAME: db2redow (SAMPLE) FUNCTION: DB2 UDB, data management, sqldRedoUpsert, probe:1867 MESSAGE : Space used: DATA #1 : Hexdump, 4 bytes 0x00002AFFDE7FBA68 : 0C01 0000 .... | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6. * **************************************************************** | |
Local-Fix: | |
none really. You would need to setup the HADR pair again by backing up the database and restoring and setting up the HADR pair again. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in Version 9.7 Fix Pack 6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.10.2011 18.06.2012 18.06.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
Problem behoben lt. FixList in der Version | |
9.7.0.6 |