...
No outage of the source database is required because the SCN is used to extract the data out of the source data. This ensures that the data will be consistent at that particular point in time. Dbvisit Replicate will start replicating at the same point in time and therefore consistency is maintained between the source and target database.
Example
This example shows how Dbvisit Replicate generates
Following commands will add test1.emp table into the current replication and generate datapump script to load data into target database. Following environment is used in this example.
| Object | Name |
|---|
| Source Database | reptest1 |
| Target Database | reptest2 |
| Database Link | reptest1_link |
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| dbvrep>ENGINE PREPARE_DP SETUP CLEAR
dbvrep>PREPARE TABLE TEST1.EMP
Connecting to running apply [TEST1.EMP]: [Apply table removed (0 metadata record(s)). Apply table added (1 metadata record(s)).]
Connecting to running mine [TEST1.EMP]: [Table prepared (321356 internal records).]
Table test1.temp instantiated at SCN 6704096
dbvrep>ENGINE PREPARE_DP WRITE DP_NETWORKLINK DIRECTORY DATA_PUMP_DIR FILE /home/oracle/reptest1/APPLY2.sh DBLINK reptest1_link USERID SYSTEM/odb10g@reptest2
Created Data Pump script /home/oracle/reptest1/APPLY1.sh, using network import. |
|
|
Above command will generate following datapump script.
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| impdp SYSTEM/odb10g@reptest2 table_exists_action=TRUNCATE network_link=reptest1_link directory=
DATA_PUMP_DIR flashback_scn=6704096 tables=TEST1.emp logfile=TEST1_temp.log JOB_NAME=DP_reptest1_0001 |
|
|