8.2 Action Required when Automatic Switch Fails (when the Mirroring Controller Option is Used)

If the system behavior is unstable, for example there are insufficient temporary system resources, the Mirroring Controller automatic switch may fail.

Perform the switch manually using one of the following methods:

Execute the mc_ctl command in switch mode
Execute the mc_ctl command in switch mode on the primary server or the standby server.
```
Example)
```
```
$ mc_ctl switch -M /mcdir/inst1
```
Note
If the server fails during execution of the mc_ctl command, automatic switch, or automatic disconnection, or if communication between the primary server and the standby server is lost, a message indicating that the mc_ctl command is being executed may be output even though the command is not running elsewhere, and the command may end abnormally.
In this case, switch the server in accordance with the “Execute the mc_ctl command in stop mode" procedure below.
Execute the mc_ctl command in stop mode
Execute the mc_ctl command in stop mode on the server on which the error occurred.
```
Example)
```
```
$ mc_ctl stop -M /mcdir/inst1
```
If the instance does not stop, refer to "Actions in Response to Failure to Stop an Instance" in the Operation Guide, and then stop the instance.
Then, specify the -e option in the mc_ctl command to forcibly stop Mirroring Controller.
```
Example)
```
```
$ mc_ctl stop -M /mcdir/inst1 -e
```

See

Recovery to database multiplexing mode

Refer to "8.1.1.2 Rebuild the Standby Server" and "8.1.1.3 Failback of the Primary Server" for information on recovery to database multiplexing mode.