If the system behavior is unstable, for example there are insufficient system resources such as available memory or free disk space, automatic disconnection using Mirroring Controller may not be possible.
Perform the disconnection manually using one of the following methods:
Refer to the procedures in "3.5 Manually Disconnecting the Standby Server".
In the primary server, execute the mc_ctl command in detach mode to perform forced disconnection.
Example)
$ mc_ctl detach -M /mcdir/inst1
Point
Even if connection cannot be established between database servers, it is possible to fence the standby server and forcibly disconnect by executing the mc_ctl command in detach mode.
In the cases below, stop Mirroring Controller and instances of the standby server database in advance so that the standby server is not fenced:
The --no-fencing option is specified when performing forced disconnection.
The heartbeat_error_action parameter in serverIdentifier.conf is set to "message" and the fencing command is not configured to be used (the fencing_command parameter is omitted in serverIdentifier.conf).
The heartbeat_error_action parameter in serverIdentifier.conf is set to "fallback".
See
Recovery to database multiplexing mode
Refer to "4.1.2.2 Rebuild the Standby Server" for information on recovery to database multiplexing mode.
