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.
Refer to “Using sp_setrepproc to copy user stored procedures” for more information.
For detailed information on what information is replicated for Oracle warm standby application, see Chapter 14, “Managing Warm Standby Applications for Oracle” in the Replication Server Heterogeneous Guide.
