Replicated Information for Warm Standby

SAP Replication Server supports different methods for enabling replication to the standby database. The level and type of information that SAP Replication Server copies to the standby database depends on the method you choose.

Optionally, you can also tell SAP Replication Server which user stored procedures to replicate to the standby database. You can copy the execution of user stored procedures to the standby database by marking the stored procedures with the sp_setrepproc system procedure. Normally, only stored procedures associated with function replication definitions are replicated to standby databases.

For detailed information on what information is replicated for Oracle warm standby, see Heterogeneous Warm Standby for Oracle in the SAP Replication Server Heterogeneous Replication Guide .

• Comparison of Replication Methods
  Compare sp_reptostandby and sp_setreptable, to learn how each copies information to the standby database.
• Use sp_reptostandby to Enable Replication
  Use sp_reptostandby to copy DML and supported DDL commands for all user tables to the standby database.
• Use sp_setreptable to Enable Replication
  Use sp_setreptable to mark individual tables for replication to replicate or replicate and standby databases.
• Use sp_setrepproc to Copy User Stored Procedures
  To copy the execution of a user stored procedure to the standby database, mark the stored procedure for replication with sp_setrepproc.
• Replication of Tables with the Same Name but Different Owners
  Adaptive Server and Replication Server allow you to replicate tables with the same name but different owners.
• Replication of text, unitext, image, and rawobject Data in Warm Standby Applications
  If a database is marked with sp_reptostandby, the replication status is automatically replicate_if_changed, and Adaptive Server logs only text, unitext, image, and rawobject columns that have been changed.
• Configure Warm Standby Database for SQL Statement Replication
  By default, warm standby applications do not replicate the DML commands that support SQL statement replication. However, there are several ways you can use SQL statement replication.
• Replication of Encrypted Columns
  Considerations when working with encrypted columns in warm standby applications are similar to non-warm standby environments.
• Replication of Quoted Identifiers
  When replicating to a warm standby database and to replication definition subscribers, and the primary table name is marked as quoted but the replicate table name is not, or vice-versa, Replication Server sends both the primary table name and the replicate table name as quoted.
• When Warm Standby Involves a Replicate Database
  You can copy information from an active database to a standby database and also copy information from the active database to a replicate database.
• Change Replication for the Current isql Session
  You can use set replication to control replication of DML and DDL commands and procedures for an isql session.