In two way replication, Dbvisit Replicate can not prepare tables for replication on the target system as they do not exist there. Thus we need to create empty tables on target. If there are a few tables to be replicated then we recommend creating those tables manually. When there are several tables to be replicated then you can use auto generated datapump script of Dbvisit Replicate with a small modification.
The steps for this are:
- Complete setup wizard
- Run the *-all.sh script which will generate APPLY.sh file with datapump script.
- Modify APPLY.sh file and add "CONTENT=METADATA_ONLY" and run on target system (this only creates the tables - DDL and does not load the data).
- Run the *-all.sh script again to prepare the tables
- Start the replication (i.e. follow the steps listed in the Nextsteps.txt file).
Running the APPLY.sh script takes place within this step. This time you don't modify the APPLY.sh script and so it actually loads the data from the source to the target database. Note that APPLY1.sh script for loading data from target to source is also generated, however it should not be run, as the data is already in the first database.
| Info |
|---|
In step 5 it has been stated that the APPLY1.sh script should not be run. This statement, however, is only true if you are configuring a simple 2-way replication. For the complex scenarios (some data does not exist in the second database, but some data exists in the second database but does not exist in the first one) the APPLY1.sh might be necessary. In such a case the data instantiation must be considered carefully. If not sure, please contact the Dbvisit Support. |
Example of using datapump for creating starting point
...