DB2 FOR LUW / DB2FORLUW / 970 - DB2

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 
mountV97_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" && 
"X$vfs" != "Xmmfs" && -z $isVgManaged ]]; then 
   # RLV 
   logger -i -p notice -t $myname "$vgname is RLV" 
   varyoffvg ${vgname?} 
... 
 
2) 
# Filesystem is unmounted or was not mounted 
if [[ "${UNAME}" == "AIX" && $concurrent != "Enhanced-Capable" 
&& "X$vfs" != "Xmmfs" && -z $isVgManaged ]]; then 
   varyoffvg ${vgname?} 
   lspvLine=$(lspv -L | grep " $vgname ") 
   vgactive=$(echo $lspvLine | awk '{print $4}') 
...

**************************************************************** 
* USERS AFFECTED:                                              * 
* AIX                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 fixpack 11                        * 
****************************************************************

Remove the '$concurrent != "Enhanced-Capable" &&' checks from 
the /usr/sbin/rsct/sapolicies/db2/mountV97_stop.ksh script on 
all nodes in the cluster.

Problem was first fixed in DB2 version 9.7 fixpack 11

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

12.01.2015
09.10.2015
09.10.2015

9.7.FP11