|
Problem IC76008
|
Status: Closed |
STOPPING AND STARTING HADR PRIMARY, WITHOUT DEACTIVATING THE DAT ABASE,CAN CAUSE THE INSTANCE TO TRAP UNDER CERTAIN CONDITIONS. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When HADR primary is stopped and started, without deactivating
the database, a small timing issue can cause the instance to
trap.
A stack similar to the following can be seen:
getIdentity
TermDbConnectEP
AppStopUsing
sqlesrspWrp
sqleUCagentConnectReset
sqljsDrdaAsDriver
sqeAgent6RunEDU
sqzEDU
sqlzRunEDU |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
to stop hadr, you can issue "deactivate db dbname" on primary |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.04.2011
06.06.2011
06.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
