|
Problem IC68593
|
Status: Closed |
DEACTIVATE TAKES A LONG TIME TO COMPLETE ON HADR STANDBY |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Deactivate takes a long time to complete on HADR standby.
The typical symptom is that one of the db2redow thread/process
will keep on working and the deactivate will wait for that to
complete.
If a db2trc is taken of that process/thread, it'll show that it
is working and processing records.
At this point, the only way to come out of this situation
quickly is to kill the instance using db2_kill or wait till
db2redow thread has completed its work. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Deactivate takes a long time to complete on HADR standby.The *
* typical symptom is that one of the db2redowthread/process *
* will keep on working and the deactivate willwait for that to *
* complete.If a db2trc is taken of that process/thread, it'll *
* show thatit is working and processing records.At this point, *
* the only way to come out of this situationquickly is to kill *
* the instance using db2_kill or wait tilldb2redow thread has *
* completed its work. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fix Pack 7. *
**************************************************************** |
| Local Fix: |
db2_kill to kill the instance. Please note, that restart of the
instance will now take time as recovery will start right from
the point where it got interrupted by the kill signal. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
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
|
| Solution |
Problem was first fixed in DB2 Version 9.5 Fix Pack 7. |
| Workaround |
db2_kill to kill the instance. Please note, that restart of the
instance will now take time as recovery will start right from
the point where it got interrupted by the kill signal. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.05.2010
15.11.2010
15.11.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
