You can use the HotStandby.AutoPrimaryAlone parameter to control whether the Primary server automatically switches to PRIMARY ALONE state or stays in PRIMARY UNCERTAIN state after it has lost contact with the Secondary server.

If AutoPrimaryAlone is set to Yes, when Primary loses contact with Secondary, Primary automatically switches automatically to the PRIMARY ALONE state. The PRIMARY ALONE state means that the Primary continues to accept transactions. If AutoPrimaryAlone is set to No, when Primary loses contact with Secondary, Primary switches automatically to the PRIMARY UNCERTAIN state.

By default, AutoPrimaryAlone is set to No.

The PRIMARY UNCERTAIN state prevents Primary from accepting new transactions or committing the currently active ones. Primary does not switch to PRIMARY ALONE state until HAC, the Watchdog, or System Administrator tells it to do so.

If AutoPrimaryAlone is set to No, the server can be set to the PRIMARY ALONE state by executing the ADMIN COMMAND 'hotstandby set primary alone' command. The ADMIN COMMAND 'hotstandby set primary alone' command does not change the value of AutoPrimaryAlone in the configuration file.

If you change the default to Yes, the Primary server state changes from PRIMARY ACTIVE to PRIMARY ALONE rather than to PRIMARY UNCERTAIN.