DB2 - Problembeschreibung
Problem IC74802 | Status: Geschlossen |
IF TABLESPACE IS NOT AVAILABLE ON STANDBY, AFTER TAKEOVER, THE T ABLESPACE ON NEW PRIMARY IS NOT IN ROLLFORWARD PENDING STATE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
The problem can be reproduced in the following steps: 1. setup HADR environment. We can assume the two instances as "Instance_Prim" and "Instance_Standby" 2. Instance_Prim: db2 create db hadrtest db2 "create tablespace tbtest managed by database using (file 'tbtest' 1M)" db2 backup db hadrtest to /TMP 3. Instance_Standby: db2 restore db hadrtest from /TMP db2 start hadr on db hadrtest as standby 4. Instance_Prim: db2 start hadr on db hadrtest as primary db2 connect to hadrtest db2 "create table hadr_prim.test (c1 int) in tbtest" 5. Instance_Standby: . db2 deactivate db hadrtest db2 stop hadr on db hadrtest chmod 000 $HOME/$DB2INSTANCE/NODE0000/SQL00001/tbtest db2 start hadr on db hadrtest as standby 6. Instance_Standby: db2 takeover hadr on db hadrtest db2 connect to hadrtest db2 list tablespaces After takeover, in step 6, the tablespace , tbtest state is offline. The correct tablespace state should be 'Rollforward Pending'. NOTE: To avoid the incorrect tablespace state, in step 5, avoid the command - "db2 stop hadr on db hadrtest". | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * The problem can be reproduced in the following steps: * * * * 1. setup HADR environment. We can assume the two instances * * as "Instance_Prim" and "Instance_Standby" * * * * 2. Instance_Prim: * * db2 create db hadrtest * * db2 "create tablespace tbtest managed by database using * * (file * * 'tbtest' 1M)" * * db2 backup db hadrtest to /TMP * * * * 3. Instance_Standby: * * db2 restore db hadrtest from /TMP * * db2 start hadr on db hadrtest as standby * * * * 4. Instance_Prim: * * db2 start hadr on db hadrtest as primary * * db2 connect to hadrtest * * db2 "create table hadr_prim.test (c1 int) in tbtest" * * * * 5. Instance_Standby: . * * db2 deactivate db hadrtest * * db2 stop hadr on db hadrtest * * chmod 000 $HOME/$DB2INSTANCE/NODE0000/SQL00001/tbtest * * * * db2 start hadr on db hadrtest as standby * * * * 6. Instance_Standby: * * db2 takeover hadr on db hadrtest * * db2 connect to hadrtest * * * * After takeover, in step 6, the tablespace, tbtest state is * * offline. The correct tablespace state should be * * 'Rollforward Pending'. * * NOTE: To avoid the incorrect tablespace state, in step 5, * * avoid the command - "db2 stop hadr on db hadrtest". * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 version 9.7 fix pack 4. * **************************************************************** | |
Local-Fix: | |
Do not run "stop hadr" in step 5 | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
The fix will be included in db2 version 9.7 fix pack 4. | |
Workaround | |
Do not run "stop hadr" in step 5 | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 02.03.2011 09.05.2011 09.05.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP4 | |
Problem behoben lt. FixList in der Version | |
9.7.0.4 |