DB2 - Problembeschreibung
Problem IC95912 | Status: Geschlossen |
THE "DB2INSTANCE -LIST" COMMAND TAKES A LONG TIME TO RETURN WHEN A CLUSTER HOST IS OFFLINE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In a pureScale environment, when a host is offline, the"db2instance -list" command is taking over 50 seconds to return. It is much slower compared to the case where all hosts are online. The command returns within 10 seconds in this case. For example, the "db2instance -list" may be seen as below when host8 was down, which took 60.33 seconds to return: /home/db2inst> time -p db2instance -list ID TYPE STATE HOME_HOST CURRENT_HOST ALERT PARTITION_NUMBER LOGICAL_PORT NETNAME -- ---- ----- --------- ------------ ----- ---------------- ------------ ------- 0 MEMBER WAITING_FOR_FAILBACK host8 host7 NO 0 1 host7.XXX.com 1 MEMBER STARTED host7 host7 NO 0 0 host7.XXX.com 2 MEMBER STARTED host10 host10 NO 0 0 host10.XXX.com 3 MEMBER STARTED host11 host11 NO 0 0 host11.XXX.com 128 CF PRIMARY host6 host6 NO - 0 host6.XXX.com 129 CF PEER host9 host9 NO - 0 host9.XXX.com HOSTNAME STATE INSTANCE_STOPPED ALERT -------- ----- ---------------- ----- host11 ACTIVE NO NO host10 ACTIVE NO NO host7 ACTIVE NO NO host9 ACTIVE NO NO host6 ACTIVE NO NO host8 INACTIVE NO YES There is currently an alert for a member, CF, or host in the data-sharing instance. For more information on the alert, its impact, and how to clear it, run the following command: 'db2cluster -cm -list -alert'. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.5 FP3 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem Fixed In DB2 v10.5 FP3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 12.09.2013 24.03.2014 24.03.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.3 | |
10.5.0.3 |