Results of a Takeover When the Partner Cluster Cannot Be Reached

This section describes the activation state of the primary and secondary clusters before and after you run a geopg takeover command when the partner cluster cannot be reached or when the protection group on the partner cluster is busy.

The following table describes the states when you run the geopg takeover command on the secondary cluster, cluster-newyork, and the primary cluster cannot be reached or the protection group on the primary cluster is busy.

Note - The cluster role and state after the takeover, which is given in the table, is available only when the partner cluster can be reached again.

Table D-3 Takeover Results of Running the geopg takeover Command on the Secondary Cluster When the Primary Cluster Cannot Be Reached

Cluster Role and State Before Takeover	Cluster Role and State After Takeover
`cluster-paris`: primary, deactivated, synchronization status `Unknown` `cluster-newyork`: secondary, deactivated, synchronization status `Unknown`	`cluster-paris`: primary, deactivated, synchronization status `Error` `cluster-newyork`: primary, deactivated, synchronization status `Error`

`cluster-paris`: primary, activated, synchronization status `Unknown` `cluster-newyork`: secondary, deactivated, synchronization status `Unknown`	`cluster-paris`: primary, activated, synchronization status `Error` `cluster-newyork`: primary, deactivated, synchronization status `Error`
`cluster-paris`: primary, deactivated, synchronization status `Unknown` `cluster-newyork`: secondary, activated, synchronization status `Unknown`	`cluster-paris`: primary, deactivated, synchronization status `Error` `cluster-newyork`: primary, activated, with data replication stopped, synchronization status `Error`
`cluster-paris`: primary, activated, synchronization status `Unknown` `cluster-newyork`: secondary, activated, synchronization status `Unknown`	`cluster-paris`: primary, activated, synchronization status `Error` `cluster-newyork`: primary, activated, with data replication stopped, synchronization status `Error`

The following table describes the states when you run the geopg takeover command on the primary cluster, cluster-paris, and the secondary cluster cannot be reached or the protection group on the secondary cluster is busy.

Table D-4 Takeover Results of Running the geopg takeover Command on the Primary Cluster When the Secondary Cluster Cannot Be Reached

Cluster Role and State Before Takeover	Cluster Role and State After Takeover
`cluster-paris`: primary, deactivated, synchronization status `Unknown` `cluster-newyork`: secondary, deactivated, synchronization status `Unknown`	`cluster-paris`: primary, deactivated, synchronization status `OK`, `Error`, or `Mismatch` `cluster-newyork`: secondary, deactivated, synchronization status `OK`, `Error`, or `Mismatch`

`cluster-paris`: primary, activated, synchronization status `Unknown` `cluster-newyork`: secondary, deactivated, synchronization status `Unknown`	`cluster-paris`: primary, activated, with data replication stopped, synchronization status `OK`, `Error`, or `Mismatch` `cluster-newyork`: secondary, deactivated, synchronization status `OK`, `Error`, or `Mismatch`
`cluster-paris`: primary, deactivated, synchronization status `Unknown` `cluster-newyork`: secondary, activated, synchronization status `Unknown`	`cluster-paris`: primary, deactivated, synchronization status `OK`, `Error`, or `Mismatch` `cluster-newyork`: secondary, activated, synchronization status `OK`, `Error`, or `Mismatch`
`cluster-paris`: primary, activated, synchronization status `Unknown` `cluster-newyork`: secondary, activated, synchronization status `Unknown`	`cluster-paris`: primary, activated, with data replication stopped, synchronization status `OK`, `Error`, or `Mismatch` `cluster-newyork`: secondary, activated, synchronization status `OK`, `Error`, or `Mismatch`

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Geographic Edition System Administration Guide Oracle Solaris Cluster 3.3 3/13