IBM Support

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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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
    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}')
    ...
    

Local fix

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

Problem summary

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

Problem conclusion

  • Problem was first fixed in DB2 version 9.7 fixpack 11
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT06424

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-12

  • Closed date

    2015-10-09

  • Last modified date

    2015-10-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IT06469 IT06470

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT06424

Modified date: 09 October 2015