We're here to help!

Step 3- Replicated Tables

Follow
Step 3 - Replicated tables
========================================
The third step is to choose 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.
 
Following tables are defined for replication pairs:
1: SOURCEDB (Oracle) ==> RDSTGT (Oracle AWS RDS), DDL: yes, suffix: (no suffix), prepare: single-scn
  No tables defined.
Enter number of replication pair to modify it, or "done": [1]

 

 

Please enter list of all individual tables to be replicated. Enter schema name(s) only to replicate all tables in that schema. Use comma or
space to delimit the entries.
Enter the tables and schemas: [] JDOE

 

 

Selected schemas: JDOE
Add more tables or schemas? (YES/NO) [NO]

 

 

To replicate changes of PL/SQL objects in schema(s), please enter the schemas to be replicated. Note that specifying any entry will cause
additional privileges to be granted to dbvrep. Enter through a comma or space-delimited list.
Enter the list of schemas (PL/SQL): []
 

 

 

You can also specify some advanced options:
1. Rename schemas or tables.
2. Specify filtering conditions.
3. (Tables only) Configure Change Data Capture; this does not maintain a copy of the source table, but logs all operations as separate
entries. This is useful for ETL or as an audit trail. This usually requires adding of new columns (timestamps, old/new values etc.) to the
target table.
Specify rename name or filter condition for any of the specified schemas (YES/NO): [no]

 

 

Following tables are defined for replication pairs:
1: SOURCEDB (Oracle) ==> RDSTGT (Oracle AWS RDS), DDL: yes, suffix: (no suffix), prepare: single-scn
  JDOE(tables)
Enter number of replication pair to modify it, or "done": [done]
Have more questions? Submit a request

Comments