A warm standby application is a pair of databases, one of which is a backup copy of the other. Client applications update the active database; Replication Server maintains the standby database as a copy of the active database.
If the active database fails, or if you need to perform maintenance on the active database or on the data server, a switch to the standby database allows client applications to resume work with little interruption.
To keep the standby database consistent with the active database, Replication Server reproduces transaction information retrieved from the active database’s transaction log. Although replication definitions facilitate replication into the standby database, they are not required. Subscriptions are not needed to replicate data into the standby database.
For information on how to set up and configure a warm standby application between two Oracle databases, see Chapter 12 “Managing Heterogeneous Warm Standby Applications” in the Replication Server Heterogeneous Guide.
