Run *-ALL SCRIPT

$ ./TEST_FETCH-all.sh
Setting up Dbvisit Replicate configuration
Configure database SOURCEDB...
This check fails if the DBID is not the expected one...
 
 
Ok, check passed.
Configure database RDSTGT...
This check fails if the DBID is not the expected one...
 
 
Ok, check passed.
Object grants for database SOURCEDB...
Object grants for database RDSTGT...
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.01.3900
Copyright (C) Dbvisit Software Limited.  All rights reserved.
DDC file /home/oracle/TEST_FETCH/config/TEST_FETCH-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 32B6B292-AF74-11E3-A3E3-AA6951CB262D. 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
1 applier SCN set.
dbvrep> SET APPLY.INSTANTIATE_SCN NOW
Variable INSTANTIATE_SCN set to NOW for process APPLY.
dbvrep> ENGINE SUPPLEMENTAL LOGGING SCHEMA JDOE 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 JDOE
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 JDOE
Table JDOE.LOADTEST instantiated at SCN 1753802
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/TEST_FETCH/APPLY.sh DBLINK SOURCEDB USERID
rds_admin/dbvisit2014@RDSTGT
Created Data Pump script /home/oracle/TEST_FETCH/APPLY.sh, using
network import.
dbvrep> create ddcdb from ddcfile
DDC loaded into database (340 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.
These steps are required after the TEST_FETCH-all.sh script runs:
 
1) Create the necessary directory(ies) on the servers:
ec2-54-82-47-176.compute-1.amazonaws.com: /home/oracle/TEST_FETCH
ip-10-139-39-29: /home/oracle/TEST_FETCH
 
2) Copy the DDC files to the server(s) where the processes will run:
ip-10-139-39-29: /home/oracle/TEST_FETCH/TEST_FETCH-APPLY.ddc
dbvlin210.dbvisit.co.nz: /home/oracle/TEST_FETCH/TEST_FETCH-FETCHER.ddc
ec2-54-82-47-176.compute-1.amazonaws.com: /home/oracle/TEST_FETCH/TEST_FETCH-MINE.ddc
 
3) Review that path to dbvrep executable is correct in the run scripts:
/home/oracle/TEST_FETCH/TEST_FETCH-run-dbvlin210.dbvisit.co.nz.sh
/home/oracle/TEST_FETCH/TEST_FETCH-run-ec2-54-82-47-176.compute-1.amazonaws.com.sh
/home/oracle/TEST_FETCH/TEST_FETCH-run-ip-10-139-39-29.sh
 
4) Copy the run script to the server(s) where the processes will run:
dbvlin210.dbvisit.co.nz: /home/oracle/TEST_FETCH/TEST_FETCH-run-dbvlin210.dbvisit.co.nz.sh
ec2-54-82-47-176.compute-1.amazonaws.com: /home/oracle/TEST_FETCH/TEST_FETCH-run-ec2-54-82-47-176.compute-1.amazonaws.com.sh
ip-10-139-39-29: /home/oracle/TEST_FETCH/TEST_FETCH-run-ip-10-139-39-29.sh
 
5) Ensure firewall is open for listen interfaces 0.0.0.0:7903, 0.0.0.0:7901, 0.0.0.0: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/TEST_FETCH/APPLY.sh
Create referenced database links (if any) before running the scripts.
 
7) Start the replication processes on all servers:
dbvlin210.dbvisit.co.nz: /home/oracle/TEST_FETCH/TEST_FETCH-run-dbvlin210.dbvisit.co.nz.sh
ec2-54-82-47-176.compute-1.amazonaws.com: /home/oracle/TEST_FETCH/TEST_FETCH-run-ec2-54-82-47-176.compute-1.amazonaws.com.sh
ip-10-139-39-29: /home/oracle/TEST_FETCH/TEST_FETCH-run-ip-10-139-39-29.sh
 
8) Start the console to monitor the progress:
/home/oracle/TEST_FETCH/start-console.sh
 
The above list is stored in /home/oracle/TEST_FETCH/Nextsteps.txt.