Resolving other common status values for an application group - assure_mimix - 10.0

Assure MIMIX Operations Guide
Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Operations Guide
Copyright
2023
First publish date
1999
Last updated
2024-03-12
Published on
2024-03-12T11:06:36.794496

The following table lists other common problems with application group status and identifies how to begin to their resolution.

Table 1. Other problem statuses which may appear in multiple columns on the Work with Application Groups display

Column Value

Description and Action

*INACTIVE

The current status of the resource group or node is inactive. This status is possible in the Repl. Status column.

  • If all columns with a status value are *INACTIVE, the application group may have been ended intentionally. Use option 9 (Start) to start the application group.
  • If this value appears only in the App Node Status column, the application resource group nodes are all inactive and all MIMIX manager jobs are also inactive. Use option 12 (Node entries) to investigate further. For more information see Resolving status for node entries.
  • If this value appears only in the Repl. Status column, logical replication is not active. Use option 13 (Data resource groups) to investigate. For more information see Resolving status for data resource group entries.

*UNKNOWN

The current status is unknown. The local node is a network node in a non-cluster application group and does not participate in the recovery domain. Its status cannot be determined.

When this status appears in all columns, do one of the following:

  • Enter the command WRKSYS. On the Work with Systems display, check the status of Cluster Services for the local system definition. If necessary, use option 9 (Start) to start cluster services.
  • Sign on to a node that is active and use the WRKAG command to check the application group status. If the status is still *UNKNOWN, use option 12 (Node entries) to check the status of Cluster Services on the node.

*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.