Table 4 lists other common problems with application group status and identifies how to begin to their resolution.
Column Value |
Description and Action |
---|---|
*ATTN |
Each column has a unique recovery. See Resolving an *ATTN status for an application group. |
*INACTIVE |
The current status of the resource group or node is inactive. This status is possible in the App Status, Data Rsc Grp Status, and Replication Status columns.
|
*INDOUBT |
The current status of the resource group is in doubt. Cluster Services may have failed or cannot determine the current status. This status is possible in the App Status and Data Rsc Grp Status columns.
|
*NOTAVAIL |
The status is not available because the local node is not participating in the IBM i cluster. When this status appears in all columns, sign on to a node that is participating in the IBM i cluster. Then use the WRKAG command to check the application group status. |
*UNKNOWN |
The current status is unknown. The status cannot be determined. This may be because the local node is not active in the IBM i cluster or the local node is a network node a in non-cluster application group and does not participate in the recovery domain. When this status appears in all columns, do one of the following:
|
*VRTSWTSTR *VRTSWTTST *VRTSWTRCY |
These values can appear in the Repl. Status column when a virtual switch procedure is in progress for an application group of type *NONCLU. These statuses are not necessarily a problem. However, complete your virtual switch testing as soon as possible to limit exposure to your environment. While virtual switch testing is in progress, replicated transactions accumulate because apply processes and access path maintenance for affected data groups are ended. These transactions must be processed during virtual switch recovery, and the virtual switch procedure must complete before any other operation such as starting, stopping, or switching can be performed for the application group. |