DB2 - Problembeschreibung
Problem IC71549 | Status: Geschlossen |
DB2PD -HADR ENHANCEMENTS DURING TAKEOVER TO DISPLAY NUMBER OF APPLICATION REMAINING TO BE FORCED OFF ON THE PRIMARY. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
Samsung Fire and Marine Insurance experienced slow graceful takeover due to large number of agents to force off on Primary. Currently, they are unable to monitor the current state of takeover and the progress of applications left to be forced off. They considered this is as an major usability issue and requests db2pd to be enhanced. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * HADR customers on ESE * **************************************************************** * PROBLEM DESCRIPTION: * * HADR customers are not able to monitor the progress of the * * Takeover on the Primary, especially the number of clients * * remaining to be forced off. * **************************************************************** * RECOMMENDATION: * * Customers can upgrade to v91fp10 to use the new db2pd * * element. * * * * Customer can also db2pd -db -applications to determine the * * current state of the applications * **************************************************************** | |
Local-Fix: | |
The fix is to introduce a new db2pd element, "ClientsRemainingOnP" to the db2pd -hadr output. This new element is only displayed during takeover on the primary. The new field reports number of applications left to be forced off. The user may use "db2pd -applications" to list details of the remaining applications. | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC71550 IC71551 IC71552 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 28.09.2010 29.04.2011 29.04.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.1.FP10 | |
Problem behoben lt. FixList in der Version | |
9.1.0.10 |