Taking Over of the Primary Database Role from a Secondary Database

You should consider a hostile takeover only in a disaster recovery scenario when the primary database is no longer available.

For details about taking over the primary database role, see "SDS Takeover Operations", earlier in this chapter.

To take over the primary database role when the operational state is disconnected

Perform one of the following actions.
- Select the secondary database in the database view pane that is to take over the role of primary database and then select the Initiate Takeover command in the Admin menu or the Secondary menu.
- Select the secondary database in the database view pane that is to take over the role of primary database and then select the Initiate Hostile Takeover command in the Admin menu.
  
  Alternatively, when the secondary system is disconnected from the primary system, the Initiate Takeover command is enabled.
If you initiated this action from the primary database, the SDS Takeover dialog, shown in the following image, is then displayed.
In the combo box, select the secondary database that is to assume the primary database role.
If you want the takeover operation to have precedence over reader processes so that the takeover is forced if conflicts exist, select the Forced option button.

By default, conditional takeovers are performed; that is, the takeover is performed only when there are no reader process conflicts. If reader or replay conflicts exist on the secondary database, the takeover operation is abandoned.
Click the OK button. Alternatively, click the Cancel button to abandon the takeover action.

If you initiated this action from a secondary database, click the OK button in the SDS warning message box if you are aware of the consequences of initiating the takeover of the primary role from the secondary database and you want to continue.

The SDS warning message box is shown in the following image. (Alternatively, click the Cancel button to abandon taking over the primary database role.)

The database view is then updated as the role change progresses.