Page Comparison

...

All the information about the replication process has been obtained and now the replication environment can be created.

Section

Column

width	5%

Column

width	95

Panel No Format

bgColor	CCC

Created file /home/oracle/orcl/orcl-MINE.ddc.


Created file /home/oracle/orcl/orcl-APPLY.ddc.


Created file /home/oracle/orcl/orcl-dbsetup_orcl_dbvisit210.sql.


Created file /home/oracle/orcl/orcl-dbsetup_orcl_dbvisit230.sql.


Created file /home/oracle/orcl/orcl-setup.dbvrep.


Created file /home/oracle/orcl/orcl-grants_orcl_dbvisit210.sql.


Created file /home/oracle/orcl/orcl-grants_orcl_dbvisit230.sql.


Created file /home/oracle/orcl/orcl-onetime.ddc.


Created file /home/oracle/orcl/orcl-run-dbvisit210.sh.


Created file /home/oracle/orcl/orcl-run-dbvisit230.sh.


Created file /home/oracle/orcl/Nextsteps.txt.


Created file /home/oracle/orcl/orcl-all.sh.


====================================================================================


Dbvisit Replicate wizard completed


Script /home/oracle/orcl/orcl-all.sh created. This runs all the above created scripts.


Please exit out of dbvrep, review and run script as current user to


setup and start Dbvisit Replicate.


====================================================================================


Optionally, the script can be invoked now by this wizard.


Run this script now? (yes/no) [NO]


dbvrep> exit

Align

the The Dbvisit Replicate wizard has completed and has created the necessary replication environment.
Exit out of dbvrep and run the *-all.sh or *all.bat script created by the wizard. If you chose the 'no lock' option for data instantiation during the Step 2 of the Setup Wizard there will be an additional script called *pre-all.sh. In the above example the script is called orcl-pre-all.sh. This script will turn on supplemental logging on the database as well as turn on table level supplemental logging. The *-pre-all.sh script should be run at a time when the database is not as active as supplemental logging will require a lock on those tables.

In the above example the script is called orcl-all.sh. This script can be run at any time to reset or recreate the replication environment. The Nextsteps.txt explains the next steps to initiate the replication.
This completes the Dbvisit Replicate setup and configuration.
Before running the script, review the created scripts as indicated by the Nextsteps.txt (shown at the end of all.* script). For example:

Review the location of dbvrep(.exe) if it differs among the nodes if RAC is used.
Check TNS_ADMIN and ORACLE_HOME paths and make sure they are correct on all the different servers involved.

After testing, consider adding the starting of dbvrep processes to init scripts on Linux/Unix to automatically start them on server reboot. (This is not needed on Windows, as processes are registered as services by default).

...

Example of running the orcl-all.sh

Section

Column

width	5%

Column

width	95

Panel No Format

bgColor	CCC

Setting up Dbvisit Replicate configuration


Configure database orcl_dbvisit210...


Configure database orcl_dbvisit230...


Object grants for database orcl...


Object grants for database orcl_dbvisit230...


Setting up the configuration


Initializing.....done


WARN-1850: No DDC DB available, dictionary table does not exist.


DDC loaded from database (0 variables).


Dbvisit Replicate


Copyright (C) Dbvisit Software Limited. All rights reserved.


DDC file /home/oracle/orcl/orcl-onetime.ddc loaded.


MINE: Cannot determine Dbvisit Replicate dictionary version. (no dictionary exists)


APPLY: Cannot determine Dbvisit Replicate dictionary version. (no dictionary exists)


dbvrep> set ON_WARNING SKIP


Variable ON_WARNING set to SKIP for process *.


dbvrep> set ON_ERROR EXIT


Variable ON_ERROR set to EXIT for process *.


dbvrep> ENGINE SETUP MINE DROP DICTIONARY


0 dictionary objects dropped.


dbvrep> ENGINE SETUP MINE CREATE DICTIONARY


dbvrep> ENGINE SETUP MINE LOAD DICTIONARY


Supplemental logging on database set.


Loading dictionary table DBRSCOL$


Loading dictionary table DBRSOBJ$


Loading dictionary table DBRSTAB$


Loading dictionary table DBRSUSER$


Loading dictionary table DBRSV_$DATABASE


dbvrep> ENGINE SETUP APPLY DROP DICTIONARY


0 dictionary objects dropped.


dbvrep> ENGINE SETUP APPLY CREATE DICTIONARY


dbvrep> ENGINE SETUP APPLY LOAD DICTIONARY


dbvrep> ENGINE PREPARE_DP SETUP CLEAR


dbvrep> ENGINE SETUP PAIR MINE AND APPLY


ID of mine proces is A8793C78-1EEB-11E1-816F-70EC8BE7EEF4.


If not using DDC in database, set MINE_UNIQUE_ID to this value.


Table dbvrep.DBRSCOL$ instantiated at SCN 20615855


Table dbvrep.DBRSOBJ$ instantiated at SCN 20615855


Table dbvrep.DBRSTAB$ instantiated at SCN 20615855


Table dbvrep.DBRSUSER$ instantiated at SCN 20615855


Table dbvrep.DBRSV_$DATABASE instantiated at SCN 20615855


1 applier SCN set.


dbvrep> PREPARE OFFLINE SCHEMA AVI


dbvrep> PREPARE OFFLINE TABLE SCOTT.AVI_OBJECTS


Table SCOTT.AVI_OBJECTS instantiated at SCN 20626026


dbvrep> ENGINE PREPARE_DP WRITE DP_NETWORKLINK DIRECTORY DATA_PUMP_DIR FILE


/home/oracle/orcl/APPLY.sh DBLINK orcl USERID SYS/oracle@orcl_dbvisit230


Created Data Pump script /home/oracle/orcl/APPLY.sh, using network import.


dbvrep> create ddcdb from ddcfile


DDC loaded into database (131 variables).


dbvrep> set ON_WARNING SKIP


Variable ON_WARNING set to SKIP for process *.


dbvrep> set ON_ERROR SKIP


Variable ON_ERROR set to SKIP for process *.


OK-0: Completed successfully.

The replication has been configured and installed. The following steps need to be done to complete and start the replication:

Section

Column

width	5%

Column

width	95

Panel

bgColor	CCC

1) Create the necessary directory(ies) on the servers:
dbvisit230: /home/oracle/orcl 
2) Copy the DDC files to the server(s) where the processes will run:
/home/oracle/orcl/orcl-MINE.ddc
/home/oracle/orcl/orcl-APPLY.ddc 
3) Review that path to dbvrep executable is correct in the run scripts:
/home/oracle/orcl/orcl-run-dbvisit230.sh
/home/oracle/orcl/orcl-run-dbvisit210.sh 
4) Copy the run script to the server(s) where the processes will run:
/home/oracle/orcl/orcl-run-dbvisit230.sh
/home/oracle/orcl/orcl-run-dbvisit210.sh 
5) Ensure firewall is open for listen interfaces dbvisit210:7901, dbvisit230:7902 used by the processes.
6) Make sure the data on apply are in sync as of time when setup was run.

Scripts for Data Pump/export/DDL were created as requested:
/home/oracle/orcl/APPLY.sh

Create referenced database links (if any) before running the scripts.
7) Start the replication processes on all servers:
/home/oracle/orcl/orcl-run-dbvisit230.sh

/home/oracle/orcl/orcl-run-dbvisit210.sh 
8) Start the console to monitor the progress:
/usr/bin/dbvrep --ddcfile /home/oracle/orcl/orcl-MINE.ddc

Run APPLY.sh script on target machine to export data from source database and load into target database to create a starting point from where replication can be initiated. Click here for more information on creating starting point.

Note
Note
If you are on 12c and during the running of the *all.sh script you get the message: WARN-1258: Insufficient privileges to do a redolog switch. Please issue it manually. That is normally as you don't have privileges for a system wide redo log switch.

Versions Compared

Old Version 3

New Version Current

Key