suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT34779 Status: Closed

DURING RESTORES SPECTRUM PROTECT SNAPSHOT SHOWS FMM0644E ERROR VARYONVG:
THE VOLUME GROUP IS ALREADY VARIED ON IN OTHER NODE

product:
FLSHCPY DB2 AGE / 5608AC6DB / 81A - DB2
Problem description:
When running Spectrum Protect Snapshot restore operations in AIX
environments with PowerHA clustering, error messages like:
FMM0644E Error on running command: 0516-1971
varyonvg: The volume group is already varied on in other node.
can be seen in the job log even though the restore operation
finishes successfully.

Customer/Support Diagnostics:

Varyon errors are reported for volume groups under PowerHA
control
for Concurrent Capable or Enhanced Concurrent Capable volume
groups. Job log will look similar to this:
FMM0644E Error on running command: varyonvg -n 
FMM0644E Error on running command:
 0516-1971 varyonvg: The volume group is already varied on in
  other node. varyoff
FMM0644E Error on running command:
 the volume group in other node and retry the varyonvg, or
  use -O flag to
FMM0644E Error on running command:
 force varyon the volume group.
FMM0644E Error on running command: hdwIntRC: 43

but will ultimately show later in the log:
Successfully finished reimporting of all Volume Groups


Spectrum Protect Versions Affected:
IBM Spectrum Protect Snapshot versions 8.1.6 and 8.1.9 on AIX

Initial Impact: Low

Additional Keywords:
TS004314302 fcm sps varyonvg FMM0644E
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All users of IBM Spectrum Protect Snapshot for Unix on AIX   *
* who restore protected application in IBM PowerHA             *
* SystemMirror cluster environment and use volume groups in    *
* concurrent mode.                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See error description.                                       *
****************************************************************
* RECOMMENDATION:                                              *
* Apply fixing level when available. This problem is currently *
* projected to be fixed in the next release. Note that this    *
* information is subject to change at the discretion of IBM.   *
****************************************************************
Local Fix:
None. Operation finishes successfully.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All users of IBM Spectrum Protect Snapshot for Unix on AIX   *
* who restore protected application in IBM PowerHA             *
* SystemMirror cluster environment and use volume groups in    *
* concurrent mode.                                             *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See error description.                                       *
****************************************************************
* RECOMMENDATION:                                              *
* Apply fixing level when available. This problem is currently *
* projected to be fixed in the next release. Note that this    *
* information is subject to change at the discretion of IBM.   *
****************************************************************
Comment
The problem has been fixed so that Spectrum Protect Snapshot for
Unix on AIX will not show misleading error messages during a
restore in IBM PowerHA SystemMirror cluster environment.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.11.2020
10.03.2021
10.03.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)