Managing Serviceguard Fifteenth Edition, reprinted May 2008

Troubleshooting Your Cluster
Solving Problems
Chapter 8434
Force Import and Deport After Node Failure
After certain failures, packages configured with VxVM disk groups will
fail to start, logging an error such as the following in the package log file:
vxdg: Error dg_01 may still be imported on ftsys9
ERROR: Function check_dg failed
This can happen if a package is running on a node which then fails before
the package control script can deport the disk group. In these cases, the
host name of the node that had failed is still written on the disk group
header.
When the package starts up on another node in the cluster, a series of
messages is printed in the package log file
Follow the instructions in the messages to use the force import option
(-C) to allow the current node to import the disk group. Then deport the
disk group, after which it can be used again by the package. Example:
vxdg -tfC import dg_01
vxdg deport dg_01
The force import will clear the host name currently written on the disks
in the disk group, after which you can deport the disk group without
error so it can then be imported by a package running on a different
node.
CAUTION This force import procedure should only be used when you are certain
the disk is not currently being accessed by another node. If you force
import a disk that is already being accessed on another node, data
corruption can result.
Package Movement Errors
These errors are similar to the system administration errors except they
are caused specifically by errors in the package control script. The best
way to prevent these errors is to test your package control script before
putting your high availability application on line.