home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT08068 Status: Geschlossen

CHANGES IN THE MOUNT AUTOMATION SCRIPTS TO SUPPORT MOUNTS BASED ON
VG'S WITH THE MULTI-NODE VARYON PROTECTION FEATURE ENABLED.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
On AIX, in the case where the HA mount points are based on 
volume groups which have the multi-node varyon protection 
feature enabled and the primary server crashes, the volume group 
will fail to be varied on on the secondary server. 
 
In the syslogs, there should be logs about the varyonvg command 
failing with rc=43(ANOTHER_NODE_VARIEDON) on the secondary if 
this is the case. 
 
This APAR change is to support the automation of mount points 
based on VG's which have the multi-node varyon protection 
feature enabled.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* AIX                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version DB2 version 10.1 fixpack 5            * 
****************************************************************
Local-Fix:
N/A
Lösung
Problem was first fixed in DB2 version 10.1 fixpack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.04.2015
28.07.2015
28.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList