Be familiar with the requirements and restrictions of Replication Server warm standby applications.
- One Replication Server manages
both the active and standby databases. Both the active and standby
databases must be from the same vendor.
- Replication Server does not switch client applications
to the standby database.
- Run the data server for the active and standby databases
on different machines. Putting the active and standby databases
on the same data server or hardware resources undermines the benefits
of the warm standby feature.
- Replication Server does not support warm standby replication between different platforms.
- SAP recommends that tables in the active and standby databases should have a
primary key defined.
- Warm standby does not
guarantee that there is no data loss. There is a possibility of data corruption on
the primary database before the data is successfully received and persisted by the
Replication Server or written to the replicate database.
- Heterogeneous warm standby does not support all Oracle datatypes and features. If
the database uses any features or datatypes that are not supported, the primary and
replicate data can become inconsistent. For information about unsupported features
and datatypes, see Replication Agent Primary Database Guide > Replication
Agent for Oracle > Oracle-Specific Considerations.