Introduction

This guide will provide you with an overview on getting started with Dbvisit Replicate and Amazon EC2 The scenario used in this guide can be illustrated as:

This document will provide you with an overview on the steps required to implement the above solution.

Source (MINE) Server

Dbvisit Replicate will be installed on the database server, from where the mine process will be configured.

Before starting the Dbvisit Replicate configuration, make sure you have the following details of the Source Database server where the mine process will be configured. (Note that in this guide it is assumed that the source server is Unix based):

Server Name
Server IP Address (Make sure that you have an internal and external IP address. Talk to your admin about firewalls.)
Oracle (Unix User) password
Source Database Name
Source TNS Alias (Make sure it is located in local tnsnames.ora) also have the full path ready
SYS password
SYSTEM password
List of Schemas or Objects you want to replicate
Sufficient disk space to store Dbvisit Replicate Mine PLOGS (default location /home/oracle/<DDC>/)
For a list of system requirements:
System Requirements

Target (APPLY) Server

Assumption is that Oracle database is installed, up and running and has a sys/system user. Also a tablespace will need to be created. Note that in this guide the the Apply server is an Oracle Linux EC2 Instance in AWS. Note that the example initial export dump and import (instantiation) of the source data into the target will be performed from the source database server using Oracle Datapump over a database link. 'Regular' export/import may also be done. Before starting with the Dbvisit Replicate configuration it is recommended to make sure you have the following information ready with regards to the Apply server and process:

EC2 - Server Name
Server IP Address (This will be the public DNS on EC2)
root (Unix User) password
oracle (Unix User) password
Target Database Name (Amazon AWS EC2 instance)
Target TNS Alias (Make sure it is located in local tnsnames.ora) also have the full path ready
SYS password
SYSTEM password
Sufficient disk space to store Dbvisit Replicate Apply PLOGS (default location /home/oracle/<DDC>/)
For a list of system requirements:
System Requirements

SOURCE TNSNAMES.ora

SOURCE_DB =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = sourceserver.com)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = SOURCE_DB)
    )
  )

EC2_TARGET =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = ec2-54-82-3-111.compute-1.amazonaws.com )(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = EC2_TARGET)
    )
  )

Amazon EC2 Instances (Apply)

The Source database is on-premise. The EC2 target instance (EC2_TARGET) will be configured to perform the APPLY inside the AWS environment.

Instance 1:SOURCE_DB SOURCE

Environment Summary:

Oracle Enterprise 11.2.0.4
Database in archivelog mode
Database called “SOURCE_DB” created
Dbvisit Replicate 2.6.0.1 installed.

Instance 2: EC2_TARGET TARGET

Environment Summary:

Oracle 11.2.0.2 (XE) installed
Database called "EC2_TARGET" created
Install Dbvisit Replicate 2.6.01 installed

TNSNAMES.ora on the EC2_TARGET

SOURCE_DB =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = sourceserver.com)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = SOURCE_DB)
    )
  )


EC2_TARGET =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = ec2-54-82-3-111.compute-1.amazonaws.com )(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = EC2_TARGET)
    )
  )

Ensure the firewall on both environments (IPTABLES) as well as the AWS security groups is configures to allow communication between these systems. Example:

root@dbvrds01:[/root] # cd /etc/sysconfig


root@dbvrds01:[/etc/sysconfig] # cat iptables
# Firewall configuration written by system-config-securitylevel
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 1521 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 7901 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 7902 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 7903 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 7904 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 8081 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 8080 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 9090 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 8443 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT

Ensure you have configured Security Group to allow the Replicate ports (7901-7904, 1521):

Dbvisit Replicate Installation/Configuration

Installing latest Dbvisit Replicate on the source on premise machine and the target EC2 instance:

root@akl:[/root] # rpm -ivh dbvisit_replicate-2.6.01-1.x86_64.rpm
Preparing...                ########################################### [100%]
   1:dbvisit_replicate      ########################################### [100%]

Please note that the main configuration (Setup Wizard) will be executed from the source (Mine) server which is also the same server hosting the source data we want to replicate to EC2.

Starting the Dbvisit Replicate Configuration

Execute “dbvrep” as the Oracle Unix account on the source server

[oracle ~]$ dbvrep
Initializing......done
Dbvisit Replicate version 2.6.01.
Copyright (C) Dbvisit Software Limited.  All rights reserved.
No DDC file loaded.
Run "setup wizard" to start the configuration wizard or try "help" to see all commands available.

Once the command line interface (dbvrep) starts, type in “setup wizard” to start the configuration process (below is an example):

Run "setup wizard" to start the configuration
wizard or try "help" to see all commands available.

dbvrep> setup wizard

This wizard configures Dbvisit Replicate.
The setup wizard creates configuration scripts, which need
to be run after the wizard ends. No changes to the databases are made before
that.
The progress is saved every time a list of databases,
replications, etc. is shown. It will be re-read if wizard is restarted and the
same DDC name and script path is selected.

Run the wizard now? [yes]

Accept end-user license agreement? (view/yes/no) [view] yes

Before starting the actual configuration, some basic
information is needed. The DDC name and script path determines where all files
created by the wizard go (and where to reread them if wizard is
rerun) and the license key determines which options are
available for this configuration.

(DDC_NAME) - Please enter a name for this replication
(suggestion: use the name of the source database): [] TEST-EC2

(LICENSE_KEY) - Please enter your license key: [(trial)]

Which Replicate edition do you want to trial (LTD/XTD/MAX):[MAX]

(SETUP_SCRIPT_PATH) - Please enter a directory for location
of configuration scripts on this machine: [/home/oracle/TEST-EC2] /home/oracle/TEST


Network configuration files were detected on this system in
these locations:

/u01/app/oracle/product/11.2.0/db_1/network/admin
/u01/app/oracle/product/10.2.0/db_1/network/admin
/u01/app/oracle/product/11.2.0/db_1/network/admin

(TNS_ADMIN) - Please enter TNS configuration directory for
this machine: [/u01/app/oracle/product/11.2.0/db_1/network/admin]

Step 1 - Describe databases
========================================
The first step is to describe databases used in the
replication. There are usually two of them (source and target).
Store SYSDBA and DBA passwords? Passwords only required
during setup and initialization? (yes/no) [yes]
Let's configure the database, describing it's type,
connectivity, user names etc.

What type of database is this? (Oracle/MySQL/SQL
Server/Oracle AWS RDS/CSV/Hadoop): [Oracle]

Please enter database TNS alias: [] SOURCE_DB

Please enter SYSDBA user name: [SYS]
Please enter password for this user: [change_on_install] ******
Please enter user with DBA role: [SYSTEM]
Please enter password for this user: [manager] ******

Connecting to database SOURCE_DB as SYSTEM to query list of
tablespaces and to detect ASM (by looking whether any redo logs or archived
logs are stored in ASM).

Enter the Dbvisit Replicate owner (this user will be created
by this script): [dbvrep]
Please enter password for this user: [dbvpasswd]

Permanent tablespaces detected on the database: USERS.
Please enter default permanent tablespace for this user:[USERS]

Temporary tablespaces detected on the database: TEMP.
Please enter default temporary tablespace for this user:[TEMP]

Following databases are now configured:
1: Oracle DZ11G, SYS/***, SYSTEM/***, dbvrep/***,
USERS/TEMP, dbvrep/, ASM:NO, TZ: +00:00

Enter the number of the database to modify it, or
"add", or "done": [add]

Let's configure the database, describing it's type,
connectivity, user names etc.

What type of database is this? (Oracle/MySQL/SQL
Server/Oracle AWS RDS/CSV/Hadoop): [Oracle]
Please enter database TNS alias: [] EC2_TARGET
Please enter SYSDBA user name: [SYS]
Please enter password for this user: [change_on_install] *******
Please enter user with DBA role: [SYSTEM]
Please enter password for this user: [manager] **********

Connecting to database EC2_TARGET as SYSTEM to query list of
tablespaces and to detect ASM (by looking whether any redo logs or archived
logs are stored in ASM).

Enter the Dbvisit Replicate owner (this user will be created
by this script): [dbvrep]
Please enter password for this user: [dbvpasswd]
 
Permanent tablespaces detected on the database: USERS.
Please enter default permanent tablespace for this user: [USERS]
Temporary tablespaces detected on the database: TEMP.
Please enter default temporary tablespace for this user: [TEMP]

Following databases are now configured:
1: Oracle SOURCE_DB, SYS/***, SYSTEM/***, dbvrep/***,
USERS/TEMP, dbvrep/, ASM:NO, TZ: +00:00
2: Oracle EC2_TARGET, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP,
dbvrep/***, ASM:NO, TZ: +00:00


Enter the number of the database to modify it, or "add", or "done": [done]

Step 2 - Replication pairs
========================================
The second step is to set source and targets for each
replication pair.

Let's configure the replication pair, selecting source and
target.

Following databases are described:
1: SOURCE_DB (Oracle)
2: EC2_TARGET (Oracle)

Select source database: [1]
Select target database: [2]
Will be DDL replication enabled? [yes]
Use fetcher to offload the mining to a different server?
(yes/no) [no]

Would you like to encrypt the data across the network (yes
or no) [no]
Would you like to compress the data across the network (yes
or no) [no]
How long do you want to set the network timeouts.
Recommended range between 60-300 seconds [60]

Lock and copy the data initially one-by-one or at a single SCN?

one-by-one : Lock tables one by one and capture SCN
single-scn : One SCN for all tables
ddl-only   : Only DDL
script for target objects
resetlogs  : Use SCN
from last resetlogs operation (standby activation, rman incomplete
recovery)                                                                                                        
(one-by-one/single-scn/ddl-only/resetlogs) [single-scn]

What data instantiation script to create?
dp_networklink : Data Pump with network link. No export
datafile is created (APPLY.sh)
dp_exp         : Data Pump with export datafile. Creates an export datafile (APPLY.sh)
exp            : Pre-datapump exp/imp with export datafile (APPLY.sh)
ddl_file       : DDL file created (APPLY.sql)
ddl_run        : DDL is automatically executed on target
load           : All replicated data is created and loaded automatically
none                                                                                                              
(dp_networklink/dp_exp/exp/ddl_file/ddl_run/load/none) [dp_networklink]
Following replication pairs are now configured:

1: SOURCE_DB (Oracle) ==> EC2_TARGET (Oracle), DDL: yes, fetcher: no,
process suffix: (no suffix), compression: no, encryption: no, network timeout:
60, prepare type: single-scn, data load: dp_networklink

Enter number of replication pair to modify it, or
"add", or "done": [done]

Step 3 - Replicated tables
========================================
The third step is to choose the schemas and tables to be
replicated. If the databases are reachable, the tables are checked for
existence, datatype support, etc., schemas are queried for tables. Note
that all messages are merely hints/warnings and may be
ignored if issues are rectified before the scripts are actually executed.
 
Following tables are defined for replication pairs:
1: SOURCE_DB (Oracle) ==> EC2_TARGET (Oracle), DDL: yes, suffix: (no suffix), prepare: single-scn
  No tables defined.

Enter number of replication pair to modify it, or
"done": [1]
Please enter list of all individual tables to be replicated.
Enter schema name(s) only to replicate all tables in that schema. Use comma or
space to delimit the entries.
Enter the tables and schemas: [] SCOTT
Add more tables or schemas? (YES/NO) [NO] NO

To replicate changes of PL/SQL objects in schema(s), please
enter the schemas to be replicated. Note that specifying any entry will cause
additional privileges to be granted to dbvrep. Enter through a
comma or space-delimited list.

Enter the list of schemas (PL/SQL): []

You can also specify some advanced options:

1. Rename schemas or tables.

2. Specify filtering conditions.

3. (Tables only) Configure Change Data Capture; this does
not maintain a copy of the source table, but logs all operations as separate
entries. This is useful for ETL or as an audit trail. This usually
requires adding of new columns (timestamps, old/new values
etc.) to the target table.

Specify rename name or filter condition for any of the
specified schemas (YES/NO): [no]

Following tables are defined for replication pairs:
1: SOURCE_DB (Oracle) ==> EC2_TARGET (Oracle), DDL: yes, suffix: (no
suffix), prepare: single-scn  SCOTT(tables)

Enter number of replication pair to modify it, or "done": [done]

Step 4 - Process configuration
========================================
The fourth step is to configure the replication processes
for each replication.

Following processes are defined:

1: MINE on SOURCE_DB
  Not configured.
2: APPLY on EC2_TARGET
  Not configured.


Enter number of process to modify it, or "done": [1]
Fully qualified name of the server for the process (usually
co-located with the database, unless mine is offloaded using fetcher):[sourceserver.com]

Server type (Windows/Linux/Unix): [Linux]
Enable email notifications about problems (yes/no)? [no]
Enable SNMP traps/notifications about problems (yes/no)?[no]

Directory with DDC file and default where to create log
files etc. (recommended: same as global setting, if possible)? [/home/oracle/TEST]

Following settings were pre-filled with defaults or your
reloaded settings:
----------------------------------------
[MINE_REMOTE_INTERFACE]: Network remote interface:sourceserver.com:7901
[MINE_DATABASE]: Database TNS: SOURCE_DB
[TNS_ADMIN] tnsnames.ora path: /u01/app/oracle/product/11.2.0/db_1/network/admin
[MINE_PLOG]: Filemask for generated plogs:
/home/oracle/TEST/mine/%S.%E (%S is sequence, %T thread, %F original
filename (stripped extension), %P process type, %N process name, %E default extension)
[LOG_FILE]: General log file: /home/oracle/TEST/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces:  /home/oracle/TEST/log/trace/dbvrep_%N_%D_%I_%U.%E

Checking that these settings are valid...

Do you want change any of the settings? [no]
Following processes are defined:
1: MINE on SOURCE_DB
Host: sourceserver.com, SMTP: no, SNMP: no

2: APPLY on EC2_TARGET
Not configured.

Enter number of process to modify it, or "done": [2]

Fully qualified name of the server for the process (usually
co-located with the database, unless mine is offloaded using fetcher):[ip-10-47-141-210] ec2-54-82-3-111.compute-1.amazonaws.com   
Server type (Windows/Linux/Unix): [Linux]
Enable email notifications about problems (yes/no)? [no]
Enable SNMP traps/notifications about problems (yes/no)?[no]
Directory with DDC file and default where to create log
files etc. (recommended: same as global setting, if possible)? [/home/oracle/TEST]

Following settings were pre-filled with defaults or your
reloaded settings:
----------------------------------------
[APPLY_REMOTE_INTERFACE]: Network remote interface:
ec2-54-82-3-111.compute-1.amazonaws.com:7902
[APPLY_DATABASE]: Database TNS: EC2_TARGET
[TNS_ADMIN]: tnsnames.ora path: /u01/app/oracle/product/11.2.0/db_1/network/admin
[APPLY_STAGING_DIR]: Directory for received plogs:  /home/oracle/TEST/apply
[LOG_FILE]: General log file: /home/oracle/TEST/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces: /home/oracle/TEST/log/trace/dbvrep_%N_%D_%I_%U.%E

Checking that these settings are valid...
Do you want change any of the  settings? [no] no

Following processes are defined:
1: MINE on SOURCE_DB
 Host: sourceserver.com, SMTP: no, SNMP: no
2: APPLY on EC2_TARGET
  Host: ec2-54-82-3-111.compute-1.amazonaws.com, SMTP: no, SNMP: no

Enter number of process to modify it, or "done": [done]

Created file /home/oracle/TEST/TEST-EC2-APPLY.ddc.
Created file /home/oracle/TEST/TEST-EC2-MINE.ddc.
Created file /home/oracle/TEST/config/TEST-EC2-setup.dbvrep.
Created file /home/oracle/TEST/config/TEST-EC2-dbsetup_SOURCE_DB.sql.
Created file /home/oracle/TEST/config/TEST-EC2-dbsetup_EC2_TARGET.sql.
Created file /home/oracle/TEST/config/TEST-EC2-grants_SOURCE_DB.sql.
Created file /home/oracle/TEST/config/TEST-EC2-grants_EC2_TARGET.sql.
Created file /home/oracle/TEST/config/TEST-EC2-onetime.ddc.
Created file /home/oracle/TEST/start-console.sh.
Created file /home/oracle/TEST/TEST-EC2-run-sourceserver.com.sh.
Created file /home/oracle/TEST/TEST-EC2-run-ec2-54-82-3-111.compute-1.amazonaws.com.sh.
Created file /home/oracle/TEST/Nextsteps.txt.
Created file /home/oracle/TEST/TEST-EC2-all.sh.
========================================================================================================================================================================================================
Dbvisit Replicate wizard completed
Script /home/oracle/TEST/TEST-EC2-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>

Review APPLY DDC file

Ensure you have the correct TNS_ADMIN details in the APPLY ddc file. In this test example environment Oracle Express is used on the APPLY server. The location of the TNS_ADMIN variable in the TEST-EC2-APPLY.ddc is:

memory_set TNS_ADMIN /u01/app/oracle/product/11.2.0/xe/network/admin

Execute TEST-EC2-all.sh script on sourceserver.com

Run the TEST-EC2-all.sh script to initialize Dbvisit Replicate and load the dbvrep repository in both the source and target. It is important that the steps above be executed before running this step.

[oracle@]$ ./TEST-EC2-all.sh
Setting up Dbvisit Replicate configuration
Configure database SOURCE_DB...
This check fails if the DBID is not the expected one...

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

Ok, check passed.
Object grants for database SOURCE_DB...
Object grants for database EC2_TARGET...
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
Copyright (C) Dbvisit Software Limited. All rights reserved.
DDC file /home/oracle/TEST/config/TEST-EC2-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 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 5B57FC60-2978-11E3-A0AD-58D8E5C48113. 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 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
Table SCOTT.EMP instantiated at SCN 1229827
Table SCOTT.DEPT instantiated at SCN 1229827
Table SCOTT.SALGRADE instantiated at SCN 1229827
Table SCOTT.LOADTEST instantiated at SCN 1229827

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/APPLY.sh DBLINK xx USERID system/xxxx@EC2_TARGET
Created Data Pump script /home/oracle/TEST/APPLY.sh, using network import.
dbvrep> create ddcdb from ddcfile
DDC loaded into database (266 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.
These steps are required after the TEST-EC2-all.sh script runs:

1) Create the necessary directory(ies) on the servers:
ec2-54-82-3-111.compute-1.amazonaws.com: /home/oracle/TEST

2) Copy the DDC files to the server(s) where the processes will run:
ec2-54-82-3-111.compute-1.amazonaws.com: /home/oracle/TESTC/TEST-EC2-APPLY.ddc
sourceserver.com: /home/oracle/TEST/TEST-EC2-MINE.ddc

3) Review that path to dbvrep executable is correct in the run scripts:
/home/oracle/TEST/TEST-EC2-run-sourceserver.sh
/home/oracle/TEST/TEST-EC2-run-ec2-54-82-3-111.compute-1.amazonaws.com.sh

4) Copy the run script to the server(s) where the processes will run:
sourceserver.com: /home/oracle/TEST/TEST-EC2-run-dbvrds01.sh
ec2-54-82-3-111.compute-1.amazonaws.com: /home/oracle/TEST/TEST-EC2-run-ec2-54-82-3-111.compute-1.amazonaws.com.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/TEST/APPLY.sh
Create referenced database links (if any) before running the scripts.

7) Start the replication processes on all servers:
sourceserver.com: /home/oracle/TEST/TEST-EC2-run-sourceserver.com.sh
ec2-54-82-3-111.compute-1.amazonaws.com: /home/oracle/TEST/TEST-EC2-run-ec2-54-82-3-111.compute-1.amazonaws.com.sh

8) Start the console to monitor the progress:
/home/oracle/TEST/start-console.sh

The above list is stored in /home/oracle/TEST/Nextsteps.txt.

Once the above scripts are created, copy the TEST-EC2-ec2-54-82-3-111.compute-1.amazonaws.com.sh and TEST-EC2-APPLY.ddc to the ec2-54-82-3-111.compute-1.amazonaws.com server, as directed by the Nextsteps.txt document.

[oracle@ ]$ scp /home/oracle/TEST/TEST-EC2-run-ec2-54-82-3-111.compute-1.amazonaws.com.sh ec2-54-82-3-111.compute-1.amazonaws.com:/home/oracle/TEST/


[oracle@ ]$ scp /home/oracle/TEST/TEST-EC2-APPLY.ddc ec2-54-82-3-111.compute-1.amazonaws.com:/home/oracle/TEST/

Instantiate Data (Import data into EC2)

The first step is to create the required database link. This link is required to pull the data from the source database into the target database. . For this database link the SYSTEM account is used.

SQL> create public database link XX connect to system identified by manager using '(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = SOURCESERVER.COM)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = SOURCE_DB)))';

Database link created.


SQL> select * from v$instance@SOURCE_DB;


INSTANCE_NUMBER INSTANCE_NAME
--------------- ----------------
HOST_NAME
----------------------------------------------------------------
VERSION         STARTUP_T STATUS    PAR   THREAD# ARCHIVE LOG_SWITCH_WAIT
----------------- --------- ------------ --- ---------- ------- ---------------
LOGINS    SHU DATABASE_STATUS       INSTANCE_ROLE     ACTIVE_ST BLO EDITION
---------- --- ----------------- ------------------ --------- --- -------
             1 SOURCE_DB
sourceserver.com
11.2.0.2.0      30-SEP-13 OPEN      NO          1 STARTED
ALLOWED    NO  ACTIVE        PRIMARY_INSTANCE   NORMAL    NO  XE

Start the import process

To import the data into the EC2 database you will need to use Datapump using the database links.

The import script was created as part of the setup wizard process. You will have a file called APPLY.sh located in the /home/oracle/TEST directory. Edit this file and add the option “exclude=statistics” at the end. This will ensure you do not get any errors at the end of the import process. Once you have updated the file and as per the above instructions you have your database links in place you can execute the script from the sourceserver.com server.

[oracle\]$ cat APPLY.sh

impdp system/xxxx@EC2_TARGET table_exists_action=TRUNCATE network_link=XX directory=DATA_PUMP_DIR flashback_scn=1229827 tables=SCOTT.EMP SCOTT.DEPT SCOTT.SALGRADE SCOTT.LOADTEST JOB_NAME=DP_EC2-TEST_0001 exclude=statistics


[oracle@]$ ./APPLY.sh
Import: Release 11.2.0.2.0 - Production on Mon Sep 30 15:45:45 2013

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
Starting "SYSTEM"."DP_C_0001":  SYSTEM/********@EC2_TARGET table_exists_action=TRUNCATE network_link=XX directory=DATA_PUMP_DIR flashback_scn=1229827 tables=SCOTT.EMP,SCOTT.DEPT, SCOTT.SALGRADE, SCOTT.LOADTEST  JOB_NAME=DP__0001 exclude=statistics
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 102.6 MB
Processing object type TABLE_EXPORT/TABLE/TABLE
. . imported "SCOTT"."EMP"                         14 rows
. . imported "SCOTT"."DEPT"                         4 rows
. . imported "SCOTT"."SALGRADE"                     5 rows
. . imported "SCOTT"."LOADTEST"                     100 rows

Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Job "DBVADMIN"."DP__0001" successfully completed at 02:46:32

Start the Replication Processes

Mine Server - sourceserver.com

[oracle@]$ ./TEST-EC2.sourceserver.com.sh
Initializing......done
[oracle@ ]$ DDC loaded from database (266 variables).
Dbvisit Replicate version 2.6
Copyright (C) Dbvisit Software Limited.  All rights reserved.
DDC file /home/oracle/TEST/TEST=EC2-MINE.ddc loaded.
Starting process MINE...Created directory /home/oracle/TEST/ddc_backup
Created directory /home/oracle/TEST/log/
Created directory /home/oracle/TEST/log/trace/
Created directory /home/oracle/TEST/mine/
started

Apply Server - EC2:

[oracle@]$ ./TEST-EC2-run-ec2-54-82-3-111.compute-1.amazonaws.com.sh
Initializing......done
DDC loaded from database (266 variables).
Dbvisit Replicate version 2.6
Copyright (C) Dbvisit Software Limited.  All rights reserved.
DDC file /home/oracle/TEST/TEST-EC2-APPLY.ddc loaded.
Starting process APPLY...Created directory /home/oracle/TEST/ddc_backup
Created directory /home/oracle/TEST/log/
Created directory /home/oracle/TEST/log/trace/
Created directory /home/oracle/TEST/apply
started

Starting the Dbvisit Replicate console

The console can be started from the Mine server (source) using the “start-console.sh” script

[oracle@ ]$ ./start-console.sh

Example output can be seen below. Note that the mine and apply process does take some time to initialize.

Once both Mine and Apply is initialized:

\ Dbvisit Replicate 2.6.01.3880(MAX edition) - Evaluation License expires in 30 days

MINE IS running. Currently at plog 141 and SCN 4587877 (03/12/2014 05:36:19).

APPLY IS running. Currently at plog 141 and SCN 4587867 (03/12/2014 05:36:17).

Progress of replication TEST-EC2:MINE->APPLY: total/this execution

--------------------------------------------------------------------------------------------------------------------------------------------

SCOTT.DEPT: 100% Mine:70/70 Unrecov:0/0 Applied:70/70 Conflicts:0/0 Last:11/03/2014 15:57:08/OK

SCOTT.EMP: 100% Mine:1/1 Unrecov:0/0 Applied:1/1 Conflicts:0/0 Last:11/03/2014 15:58:43/OK

--------------------------------------------------------------------------------------------------------------------------------------------

Testing the replication

Insert some rows into the source tables.

Replication is now up and running.

Browser not supported