DB2 - Problembeschreibung
Problem IC76008 | Status: Geschlossen |
STOPPING AND STARTING HADR PRIMARY, WITHOUT DEACTIVATING THE DAT ABASE,CAN CAUSE THE INSTANCE TO TRAP UNDER CERTAIN CONDITIONS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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 | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 9.7 Fix Pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 26.04.2011 06.06.2011 06.06.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |