Replicated Information for Warm Standby

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

You must choose one of these two methods:

Use the sp_reptostandby system procedure to mark the entire database for replication to the standby database. sp_reptostandby enables replication of data manipulation language (DML) commands and a set of supported data definition language (DDL) commands and system procedures.
- DML commands, such as insert, update, delete, and truncate table, change the data in user tables.
- DDL commands and system procedures change the schema or structure of the database.
sp_reptostandby allows replication of DDL commands and procedures that make changes to system tables stored in the database. You can use DDL commands to create, alter, and drop database objects such as tables and views. Supported DDL system procedures affect information about database objects. They are executed at the standby database by the original user.
If you choose not to use sp_reptostandby, you can mark individual user tables for replication with sp_setreptable. This procedure enables replication of DML operations for the marked tables.

Optionally, you can also tell 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 Replication Server Heterogeneous Guide > Heterogeneous Warm Standby for Oracle.

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.

Parent topic: Manage Warm Standby Applications

Related concepts

Use sp_setrepproc to Copy User Stored Procedures