Step 3 - Replicated Tables

Owned by Copy Space for Confluence
Last updated: Mar 01, 2016 by Donna Zehl (Unlicensed)
2 min read

The following settings are available in "Step 3 - Replicated tables" of the setup wizard.

This step chooses the schemas and tables to be replicated. If the databases are reachable, the tables are checked for existence, datatype support, etc., schemas are queried for tables. Note that all messages are merely hints/warnings and may be ignored if issues are rectified before the scripts are actually executed.

Enter number of replication pair to modify it, or "done":

This will list the replication pairs defined in previous step. 

Enter the tables and schemas:

Enter a list of individual tables to be replicated. Enter schema name(s) to replicate all tables in that schema. Both tables names and schemas can be entered on a single line. Table names must be prefixed with a schema name. 
Use comma or space to delimit the entries. 

Add more tables or schemas? (YES/NO)

More tables or schemas can be added. If the list is complete, choose No.

Enter the list of schemas (PL/SQL)

PL/SQL procedures, functions and packages can also be replicated. Enter through a comma or space-delimited list. Note that the original PL/SQL will not be replicated, only the changes. 

** NOTE: PL/SQL replication only if entire schema & not table level replication is defined.

Specify rename name, filter condition, CDC/Audit/ETL for any of the specified tables (yes/no)

The following options are available:

  • rename name : This allows the replicated table to have a different name.
  • filter condition: This can specify a filter condition to only replicate data when the filter condition is true.
  • CDC/Audit/ETL : This replicates the changes as individual entries into a staging or audit table. Every insert, update or delete will appear as a separate entry in the staging or audit table.