|
Problem IT06469
|
Status: Closed |
ENHANCED-CAPABLE(EC) VG'S CAN REMAIN VARIED-ON IN READ-WRITE MODE ON THE STANDBY NODE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| Solution |
Problem was first fixed in DB2 version 10.1 fixpack 5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.01.2015
28.07.2015
28.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
