This appendix does not consider all of the many possible configurations, options, and scenarios that can affect failover and failback procedures. It also does not consider the impact and interaction of any other system that might share resources with, or have some interdependency with the Mirror Activator for Oracle system.
This appendix describes only failover and failback tasks that are specific to the Mirror Activator for Oracle system. General failover and failback tasks, such as re-routing network connections and switching client access from one database to another, are not covered in this document.
The procedures in this appendix assume that:
All Mirror Activator for Oracle system components are set up and properly configured, as described in Chapter 2, “Setup and Configuration.”Also, when functioning normally, the Mirror Activator for Oracle system is capable of replicating transactions from the primary database to the standby database, with no replication failures.
The disk replication system is set up and configured to mirror all data devices, and to mirror all log devices to both the local site and the mirror log device site.
The Mirror Activator for Oracle system is essentially self-contained:
It is capable of operating independently of other systems and databases outside of its control.
It shares no system resources (including servers, networks, devices, and disk replication system facilities) with other systems that reside at the primary and standby sites.
All Mirror Activator for Oracle system components—the primary and standby databases and all of their devices, disk replication system and mirror log devices, Mirror Replication Agent, and Replication Server—are dedicated solely to the Mirror Activator for Oracle system.
Additional assumptions may apply to specific procedures in this appendix.
