|
Problem IC74871
|
Status: Geschlossen |
DB2INSTANCE -LIST SHOWING MISLEADING STATUS FOR SECONDARY CF DURING MEMBER FAIL OVER. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problembeschreibung: |
The db2instance -list command shows misleading status for
secondary CF during member fail over.
The state of secondary CF should stay at CATCHUP during member
fail over when there is no database attachment, and should
remain at PEER state when there is a db attachment.
$ db2instance -list
ID TYPE STATE HOME_HOST CURRENT_HOST
-- ---- ----- --------- ------------
0 MEMBER STARTED host2 host2
1 MEMBER STARTED host3 host3
128 CF PRIMARY host1 host1
129 CF CATCHUP host4 host4 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All who uses pureScale feature. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The db2instance -list command shows misleading status for *
* secondary CF during member fail over. *
* The state of secondary CF should stay at CATCHUP during *
* member fail over when there is no database attachment, and *
* should remain at PEER state when there is a db attachment. *
* *
* $ db2instance -list *
* ID TYPE STATE HOME_HOST CURRENT_HOST *
* -- ---- ----- --------- ------------ *
* 0 MEMBER STARTED host2 host2 *
* 1 MEMBER STARTED host3 host3 *
* 128 CF PRIMARY host1 host1 *
* 129 CF CATCHUP host4 host4 *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to V9.8 FixPack 4 or later. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
|
| Lösung |
This problem is first fixed in V9.8 Fixpack 4. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 06.03.2011
09.05.2017
09.05.2017 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.8.FP4
|
| Problem behoben lt. FixList in der Version |
| 9.8.0.4
|
 |
