Page Comparison

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.
Note the following assumptions are made in this wizard – 
which can be modified by editing the resulting script:
1. All replicated tables have a primary key defined.
2. All columns of the tables and all tables of the specified schemas are replicated, 
and if DDL support is enabled, whenever a
new column/table is added, this should be replicate as well.
3. If an apply conflict arises, the default option is to try again repeatedly, 
until a different option is given or the
underlying issue is resolved. 
4. If an apply conflict arises, no more data will be replicated until the issue is resolved or ignored.
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/newvalues etc.) to the target table. 
Dbvisit Replicate can create the target table with the additional columns during setup by
selecting "ddl_run" in the data copy section of Step 2.
Following tables are defined for replication pairs:
1:orcl_dbvisit210 (Oracle) ==> orcl_dbvisit230 (Oracle), 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: [] scott.avi_objects,avi