A switchover consists of the following actions:
Application services are unmanaged on the former primary cluster.
The replication role is reversed and now continues to run from the new primary.
Application services are brought online on the new primary cluster.
When you run the geopg switchover command, the software confirms that the secondary cluster does indeed allow the replication role reversal. The command creates copies of the replicated source projects and exports the shares for use on the target appliance to ensure that no projects and mount point conflicts can occur. The command then destroys such created clones on the target appliance and confirms that the actual reverse replication operation can be performed on the target appliance.
For Oracle Data Guard, before the switchover, the command checks that the remote database is in an enabled state in the Oracle Data Guard Broker configuration. The command also confirms that the configuration is healthy by issuing the Oracle Data Guard command-line interface ( dgmgrl ) show configuration command to ensure that the command returns a SUCCESS state. If the output from this command indicates that Oracle Data Guard Broker is busy performing its own health check, the Oracle Data Guard command-line interface retries the command until it receives a SUCCESS response or until two minutes have passed. If the command-line interface is unable to get a SUCCESS response, the command fails.
For Oracle ZFS Storage Appliance, the command creates copies of the replicated source projects and exports the shares for use on the target appliance to ensure that no projects and mount point conflicts can occur. The command then destroys such created clones on the target appliance and confirms that the actual reverse replication operation can be performed on the target appliance.
The software performs the following actions on the original primary cluster:
For Availability Suite, removes affinities and resource dependencies between all the application resource groups in the protection group and the internal resource group, such as the lightweight resource groups
Takes offline the application resource groups in the protection group and places them in the Unmanaged state.
Performs a switchover to the secondary cluster for each replication configuration in the protection group.
On the original secondary cluster, the command takes the following actions:
Runs the script that is defined in the RoleChange_ActionCmd property
Brings online all application resource groups in the protection group
If the command completes successfully, the secondary cluster becomes the new primary cluster for the protection group. The original primary cluster becomes the new secondary cluster. The application resource groups in the protection group are brought online on the new primary cluster and replication from the appliance that is connected from the new primary cluster to the new secondary cluster begins.
For Oracle Data Guard, databases that are associated with the Oracle Data Guard Broker configurations of the protection group have their role reversed according to the role of the protection group on the local cluster. For HA for Oracle configurations, the dataguard_role resource property is also updated with the status of the new primary and standby clusters. The shadow Oracle database server resource group and any other application resource groups in the protection group are online on the new primary cluster. Data replication from the new primary cluster to the new standby cluster begins.
The geopg switchover command returns an error if any of the previous operations fails. Run the geoadm status command to view the status of each component. For example, the Configuration status of the protection group might be set to Error, depending on the cause of the failure. The protection group might be activated or deactivated.
If the Configuration status of the protection group is set to Error, revalidate the protection group by using the procedures that are described in Validating a Protection Group in Oracle Solaris Cluster Geographic Edition Installation and Configuration Guide .
If the configuration of the protection group is not the same on each partner cluster, you need to resynchronize the configuration by using the procedures that are described in Resynchronizing a Protection Group.