Final Wrap-up

Owned by KrupeshD (Unlicensed)
Last updated: Jun 21, 2014 by Chris Lawless (Unlicensed)
3 min read

Final wrap-up

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

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

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).

Outcome of running the scripts created by the setup wizard.

Running the *-all.sh script will configure and initiate the replication. It does the following:

  • Create the Dbvisit Replicate schemas in the source and target databases (default username dbvrep)
  • Grant the necessary privileges to the Dbvisit Replicate schema.
  • Create the Dbvisit Replicate repository in the source and target databases.
  • Load the Dbvisit Replicate configuration file (DDC) into the Dbvisit Replicate repository. The DDC file is like the init.ora for Oracle and contains the settings for the replication.
  • Prepare the schemas or objects for replication.

Example of running the orcl-all.sh

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.
  • 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.