If you are replicating from a warm standby primary environment to a replicate database outside the warm standby environment, you may want to create a new replication definition for each table to be replicated.
Mappings from Oracle datatypes to Replication Server user-defined datatypes (UDD) are provided.
By default, tables with clob/blob columns are defined with the always_replicate clause. If auto_create_repdefs is set to “on”, then clob/blob columns are defined with replicate_if_change clause.
The replication definitions are created with the send standby replication definition columns clause.
These are the cases in which you may want to create additional replication definitions:
Provide mappings from Oracle datatypes to Replication Server UDD.
Use replicate_if_change clause for table with clob/blob column.
Include the send standby all columns clause, if a database level subscription is used to subscribe to the non-warm standby database.
Specify the primary and replicate function owner. Customize the function string to specify the target (standby database) function owner information for user procedures.
create replication definition rep1 with primary at ordb.pdb with all tables named 'USER1'.'TB1' ( "COL1" int, "COL2" int, "COL3" int, "COL4" char(255), "COL5" rs_oracle_datetime, ) primary key( "COL1","COL2","COL3") searchable columns( "COL1","COL2","COL3","COL5") send standby replication definition columns replicate minimal columns go
In this example, the clause send standby replication definition columns in create replication definition command specifies that this replication definition can be used for a subscribed database as well as for a standby database.