9.4 monact (starts a server in the wait state as the active server)

Format

monact server-alias-name

Users who can execute the command

Superuser

Description

The monact command starts one of the following types of servers as the active server:

• Standby server placed in the active server start wait state

  If a server defined in the server environment definition as a standby server cannot check the status of the active system during startup processing due to an error (such as a communication error), it is placed in the wait state until the active server in the active system has started. This command forcibly starts such a standby server that is in the wait state as the active server.

• Standby server placed in the grouped-system switchover wait state

  If a failure occurs on a server for which no_exchange is specified in the group operand in the server environment definition, the standby servers in the standby system are placed in the grouped-system switchover wait state. This command forcibly starts such a standby server that is in the wait state as the active server.

• Active server placed in the hot-standby wait state

  If host reset fails, the standby server in the standby system is switched in as the active server but then is placed in the hot-standby wait state. This command forcibly starts this active server that is in the wait state as the active server.

• Standby server started in the online serverless mode (startup complete state)

  This command starts a standby server started in the online serverless mode as the active server.

Options

• server-alias-name

  Specifies the server alias name of the server that is to be started as the active server.

Return codes

Notes

• Before you execute the monact command, make sure that no active server is running in the remote host. If you execute the monact command without checking for an active server in the remote host, you might end up with two active servers running at the same time.

• You can execute the monact command only on servers in the following statuses:

  • Standby server in the active server start wait state

  • Standby server in the grouped-system switchover wait state

  • Active server in the hot-standby wait state

  • Standby server started in the online serverless mode

• The monact command cannot be executed on a server in the resource server start wait state.

• The return code is also set to 0 when any of the following messages is issued while type2 is specified in the exitcode operand in the HA Monitor environment settings:

  KAMN227-E, KAMN322-E, KAMN339-E, KAMN456-E, KAMN465-E

• The active server does not start at the same time that the monact command's return code is received.