Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section initialises and starts the replication processes

1. Go in to the home directory of the replication that has been setup by the setup wizard

No Format
su - oracle
No Format
cd ~oracle/dbvrep_orcl

 

2. The configuration scripts can be inspected if needed. They are in the ./config directory. 

...

  • SQL scripts. These scripts will run SQL statements in the source or target databases. 
  • CFG scripts. These are used in the setup wizard to remember user inputs. The setup wizard can be run again and the previous input will be displayed based on information in the .cfg files. 
  • DDC scripts. These scripts contain all the configurational settings for the replication. 
  • DBVREP script. This script runs Dbvisit Replicate commands and initialises the replication.

 

3. The dbvrep_orcl-all.sh is the main script that calls all the other script to initialise the replication. Start this script

No Format
cd ~oracle/dbvrep_orcl
No Format
./dbvrep_orcl-all.sh

 

4. The replication is now being initialised. This takes approximately 3-5 minutes.

No Format
Setting up Dbvisit Replicate configuration
Configure database ttorcl_src...
This check fails if the DBID is not the expected one...

Ok, check passed.
Configure database ttorcl_trg...
This check fails if the DBID is not the expected one...

Ok, check passed.
Object grants for database ttorcl_src...
Object grants for database ttorcl_trg...
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 version 2.6.00.3735
Copyright (C) Dbvisit Software Limited.  All rights reserved.
DDC file /home/oracle/dbvrep_orcl/config/dbvrep_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> #clear the no-DDC-DB-available warning
dbvrep> engine clear previous warnings
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 SWITCH_REDOLOG
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 DBRSIND$
Loading dictionary table DBRSOBJ$
Loading dictionary table DBRSTAB$
Loading dictionary table DBRSUSER$
Loading dictionary table DBRSV_$DATABASE
ID of mine proces is 86E1BF73-6BAB-11E3-BF96-B392B0702394. If not using
DDC in database, set MINE_UNIQUE_ID to this value.
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
WARN-1381: Looks like table 114274 is not an IOT after all. No data
found in SQL ' select obj_ from DBRSIND$ where bo_ = ? and
bitand(type_,4) != 0  and ? between valid_from_scn and valid_to_scn and
DDC_ID = ? and MINE_PROCESS_NAME = ? '
WARN-1381: Looks like table 114334 is not an IOT after all. No data
found in SQL ' select obj_ from DBRSIND$ where bo_ = ? and
bitand(type_,4) != 0  and ? between valid_from_scn and valid_to_scn and
DDC_ID = ? and MINE_PROCESS_NAME = ? '
WARN-1381: Looks like table 114338 is not an IOT after all. No data
found in SQL ' select obj_ from DBRSIND$ where bo_ = ? and
bitand(type_,4) != 0  and ? between valid_from_scn and valid_to_scn and
DDC_ID = ? and MINE_PROCESS_NAME = ? '
1 applier SCN set.
dbvrep> SET APPLY.INSTANTIATE_SCN NOW
Variable INSTANTIATE_SCN set to NOW for process APPLY.
dbvrep> ENGINE SUPPLEMENTAL LOGGING SCHEMA OE ENABLE PRIMARY KEY
dbvrep> ENGINE SWITCH_REDOLOG
dbvrep> ENGINE WAIT_SCN_FLIP
Waited 2 seconds until scn_to_timestamp changed.
dbvrep> #single-scn instantiation: lock all tables and schemas
dbvrep> ENGINE LOCK SCHEMAS OE
Locking all schemas.
Lock done.
dbvrep> #single-scn instantiation: unlock all tables and schemas, but
keep the SCN
dbvrep> ENGINE LOCK RELEASE LOCKS
dbvrep> 
dbvrep> #prepare the tables (we use OFFLINE as neither MINE not APPLY
is running; with OFFLINE we won't wait on network timeout)
dbvrep> PREPARE OFFLINE SCHEMA OE
dbvrep> #single-scn instantiation: unlock all tables and schemas,
forget the SCN (so it does not affect any further PREPARE statements)
dbvrep> ENGINE LOCK CLEAR SCN
dbvrep> ENGINE SWITCH_REDOLOG
dbvrep> #prepare script for instantiation
dbvrep> ENGINE PREPARE_DP WRITE DP_NETWORKLINK DIRECTORY DATA_PUMP_DIR
FILE /home/oracle/dbvrep_orcl/APPLY.sh DBLINK ttorcl_src USERID
SYSTEM/oracle@ttorcl_trg
Created Data Pump script /home/oracle/dbvrep_orcl/APPLY.sh, using
network import.
dbvrep> create ddcdb from ddcfile
DDC loaded into database (312 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, but some operation(s) raised warnings and/or errors.

 

5. At the end of the output, the Next Steps to be completed will be shown. These will be done carried out in the next stepsfollowing instructions

No Format
These steps are required after the dbvrep_orcl-all.sh script runs:
1) Create the necessary directory(ies) on the servers:
target: /home/oracle/dbvrep_orcl

2) Copy the DDC files to the server(s) where the processes will run:
target: /home/oracle/dbvrep_orcl/dbvrep_orcl-APPLY.ddc
source: /home/oracle/dbvrep_orcl/dbvrep_orcl-MINE.ddc

3) Review that path to dbvrep executable is correct in the run scripts:
/home/oracle/dbvrep_orcl/dbvrep_orcl-run-source.sh
/home/oracle/dbvrep_orcl/dbvrep_orcl-run-target.sh

4) Copy the run script to the server(s) where the processes will run:
source: /home/oracle/dbvrep_orcl/dbvrep_orcl-run-source.sh
target: /home/oracle/dbvrep_orcl/dbvrep_orcl-run-target.sh

5) Ensure firewall is open for listen interfaces 0.0.0.0:7902, 0.0.0.0:7901 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/dbvrep_orcl/APPLY.sh
Create referenced database links (if any) before running the scripts.

7) Start the replication processes on all servers:
source: /home/oracle/dbvrep_orcl/dbvrep_orcl-run-source.sh
target: /home/oracle/dbvrep_orcl/dbvrep_orcl-run-target.sh

8) Start the console to monitor the progress:
/home/oracle/dbvrep_orcl/start-console.sh
The above list is stored in /home/oracle/dbvrep_orcl/Nextsteps.txt.

 

6. On the target server (dbv02) create the /home/oracle/dbvrep_orcl directory

No Format
su - oracle
No Format
[oracle@target ~]$ mkdir /home/oracle/dbvrep_orcl
[oracle@target ~]$ 

 

7. On the source server (dbv01), copy the DDC file to the target server using scp. The Dbvisit Database Configuration file contains all the configurational settings for the replication. The scp password is oracle. 

No Format
[oracle@source dbvrep_orcl]$ scp /home/oracle/dbvrep_orcl/dbvrep_orcl-APPLY.ddc oracle@target-int:/home/oracle/dbvrep_orcl/
The authenticity of host 'target-int (10.1.1.11)' can't be established.
RSA key fingerprint is 07:15:bb:a2:a6:ba:60:3f:c3:31:a9:c9:4a:7c:51:6a.
No Format
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'target-int,10.1.1.11' (RSA) to the list of known hosts.

The scp password is oracle

No Format
oracle@target-int's password: 
dbvrep_orcl-APPLY.ddc

 

8. On the source server (dbv01), copy the dbvrep_orcl-run-target.sh file to the target server using scp. The scp password is oracle

No Format
[oracle@source dbvrep_orcl]$ scp /home/oracle/dbvrep_orcl/dbvrep_orcl-run-target.sh oracle@target-int:/home/oracle/dbvrep_orcl/

The scp password is oracle

No Format
oracle@target-int's password: 
dbvrep_orcl-run-target.sh 
Note

The word "target" in dbvrep_orcl-run-target.sh is dependent on your target hostname. In this case, the target hostname is called target

 

 

 

...