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 IT06469 Status: Geschlossen

ENHANCED-CAPABLE(EC) VG'S CAN REMAIN VARIED-ON IN READ-WRITE MODE ON
THE STANDBY NODE.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
During failover, DB2 leaves non-concurrent Enhanced-Capable(EC) 
volume groups(VGs) in varied-on mode on the standby node. As a 
result, this introduces the possibility of unexpected changes to 
the DB2 files on the affected file systems. This APAR addresses 
this issue by allowing non-concurrent EC VGs to be varied off 
during a DB2 failover. 
 
This is achieved by removing the following check from the 
mountV10_stop.ksh script: 
'$concurrent != "Enhanced-Capable" &&' 
 
This check is being made in two places: 
1) 
################################################################ 
# Start main... 
rc=0 
 
if [[ "${rlv}" == "true" && $concurrent != "Enhanced-Capable" && 
"$fstype" != "gpfs" && -z $isVgManaged ]]; then 
   # RLV 
   varyoffvg ${vgname?} 
   rc=$? 
   return $rc 
... 
 
2) 
# Filesystem is unmounted or was not mounted 
if [[ "${UNAME}" == "AIX" && $concurrent != "Enhanced-Capable" 
&& "$fstype" != "gpfs" && -z $isVgManaged ]]; then 
   varyoffvg ${vgname?} 
   lspvLine=$(lspv -L | grep " $vgname ") 
   vgactive=$(echo $lspvLine | awk '{print $4}') 
...
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* AIX                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version DB2 version 10.1 fixpack 5            * 
****************************************************************
Local-Fix:
Remove the '$concurrent != "Enhanced-Capable" &&' checks from 
the /usr/sbin/rsct/sapolicies/db2/mountV10_stop.ksh script on 
all nodes in the cluster.
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:
13.01.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