Oracle to Google Cloud SQL Replication Setup Example

Owned by Mike Donovan (Deactivated)
Last updated: Jan 22, 2016 by Chris Lawless (Deactivated)
13 min read

Before starting replication, the source and target environments must be in sync. If source objects are not empty then source data must be loaded into the target (the Google Cloud SQL) MySQL database. One option is to use Navicat Premium to load this data or, alternatively, export and then import CSV files.

Click here for prerequisite checklist.

Setup Wizard Example

This example shows an Oracle-to-Google-Cloud-SQL one-way replication using the following information.

Server/DatabaseName
Source databaseeleven (Oracle)
Source serverdbvlin828 (Linux)
Target databaserq-2180 (Google Cloud SQL) - note that a MySQL "database" roughly correlates to a schema in Oracle
Target serverdbvlin823 (Linux) - note that in this example the APPLY process runs on another local/on-premise server, but it is possible to move the APPLY process itself (and even the MINE as well) to a Google Cloud (Compute Engine) VM.
TNS alias for source database   eleven

 

Throughout the wizard, defaults are shown in [brackets]. Just press enter to accept them. The replication name in this example is "dbvrep_google".

 

First of all start the Dbvisit Replicate command line console.

oracle@dbvlin828[/home/oracle/dbvrep_google]: dbvrep
Initializing......done
Dbvisit Replicate version 2.8.00
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.

 

Then start the setup wizard and follow the instructions. Most of the defaults can be chosen.

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: [] dbvrep_google
(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/dbvrep_google]

Network configuration files were detected on this system in these locations:
/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]

In Step 1 we can select Google Cloud SQL as a database option for use with Dbvisit Replicate. In this example I have used the IP for this managed database service directly (displayed on the Google Cloud SQL overview console screen) but you could, alternatively, map this to a server name on your host machine(s).


Specify databases participating in the replication in the first step of setup wizard.

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 its type, connectivity, user names etc.
What type of database is this? (Oracle/MySQL/Google Cloud SQL/SQL Server/Oracle AWS RDS/CSV/Hadoop): [Oracle]
Please enter database TNS alias: [] eleven
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 eleven 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 eleven, 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 its type, connectivity, user names etc.
What type of database is this? (Oracle/MySQL/Google Cloud SQL/SQL Server/Oracle AWS RDS/CSV/Hadoop): [Oracle] Google Cloud SQL
Please enter database hostname: [localhost] 104.154.45.166
Please enter user name of an administrator: [root] oracle
Please enter password for this user: [] ******
Enter the user to log into apply database: [root] oracle
Please enter password for this user: [password] ******
Enter the database (schema) to use for Dbvisit Replicate internal data (will be created in the script): [dbvrep]

Following databases are now configured:
1: Oracle eleven, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:No, TZ: +00:00
2: Google Cloud SQL host=104.154.45.166, oracle/***, oracle/***, oracle/***, /, dbvrep/, ASM:n/a, TZ:
Enter the number of the database to modify it, or "add", or "done": [done]

 

In the second step of the setup wizard we configure replication pairs by specifying the source and target databases. Only Oracle databases can be the source here.

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: eleven (Oracle)
2: host=104.154.45.166 (Google Cloud SQL) (cannot be source, is not Oracle)
Select source database: [1]
Select target database: [2]
Will limited DDL replication be enabled? (Yes/No) [Yes]
Use fetcher to offload the mining to a different server? (Yes/No) [No]
Should where clauses (and change auditing) include all columns, not just changed and PK? (Yes/No) [No]
Would you like to encrypt the data across the network? (Yes/No) [No]
Would you like to compress the data across the network? (Yes/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)
no-lock    : Do not lock tables. Captures previous SCN of oldest active transaction. Requires pre-requisite running of pre-all.sh script                                                               (one-by-one/single-scn/ddl-only/resetlogs/no-lock) [single-scn]

What data instantiation script to create?
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                                                                                                                                                                                                   (ddl_file/ddl_run/load/none) [ddl_file] none

Following replication pairs are now configured:
1: eleven (Oracle) ==> host=104.154.45.166 (Google Cloud SQL), DDL: Yes, fetcher: No, process suffix: (no suffix), compression: No, encryption: No, network timeout: 60, prepare type: single-scn,
data load: none
Enter number of replication pair to modify it, or "add", or "done": [done]

 

In the third step of setup wizard, specify the tables/schema to be replicated. In this example, it is the TEST1 and TEST2 tables of the test schema we are using, HR.

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: eleven (Oracle) ==> host=104.154.45.166 (Google Cloud SQL), 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: [] HR.TEST1, HR.TEST2
Selected tables: HR.TEST1,HR.TEST2
Add more tables or schemas? (Yes/No) [No]

You can also specify some advanced options:
1. Exclude some tables from schema-level replication
2. Rename schemas or tables.
3. Specify filtering conditions.
4. (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, filter condition or audit for any of the specified tables? (Yes/No) [No]

Following tables are defined for replication pairs:
1: eleven (Oracle) ==> host=104.154.45.166 (Google Cloud SQL), DDL: Yes, suffix: (no suffix), prepare: single-scn
  HR.TEST1, HR.TEST2
Enter number of replication pair to modify it, or "done": [done]

In Step 4 we need to be sure to change the server for the APPLY process to where this will run from (i.e dbvlin823 in this test example) away from the default, which is the IP/hostname for the Google Cloud SQL database. Note that Google Cloud SQL is a managed database service which we connect through to as an endpoint, and we do not access the underlying server on which this is running.

In the fourth and the final step of setup wizard, we can configure MINE and APPLY process parameters.

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

Following processes are defined:
1: MINE on eleven
  Not configured.
2: APPLY on host=104.154.45.166
  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): [dbvlin828.dbvisit.co.nz] dbvlin828
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/dbvrep_google]

Following settings were pre-filled with defaults or your reloaded settings:
----------------------------------------
[MINE_REMOTE_INTERFACE]: Network remote interface: dbvlin828:7901
[MINE_DATABASE]: Database TNS: eleven
[TNS_ADMIN]: tnsnames.ora path: /u01/app/oracle/product/11.2.0/db_1/network/admin
[MINE_PLOG]: Filemask for generated plogs: /home/oracle/dbvrep_google/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/dbvrep_google/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces: /home/oracle/dbvrep_google/log/trace/dbvrep_%N_%D_%I_%U.%E

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

Following processes are defined:
1: MINE on eleven
  Host: dbvlin828, SMTP: No, SNMP: No
2: APPLY on host=104.154.45.166
  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): [104.154.45.166] dbvlin823
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/dbvrep_google]

Following settings were pre-filled with defaults or your reloaded settings:
----------------------------------------
[APPLY_REMOTE_INTERFACE]: Network remote interface: dbvlin823:7902
[APPLY_DATABASE]: Database MySQL connection string: database=dbvrep;host=104.154.45.166
[TNS_ADMIN]: tnsnames.ora path: /u01/app/oracle/product/11.2.0/db_1/network/admin
[APPLY_SCHEMA]: Dbvisit Replicate database (schema): dbvrep
[APPLY_STAGING_DIR]: Directory for received plogs: /home/oracle/dbvrep_google/apply
[LOG_FILE]: General log file: /home/oracle/dbvrep_google/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces: /home/oracle/dbvrep_google/log/trace/dbvrep_%N_%D_%I_%U.%E

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

Following processes are defined:
1: MINE on eleven
  Host: dbvlin828, SMTP: No, SNMP: No
2: APPLY on host=104.154.45.166
  Host: dbvlin823, SMTP: No, SNMP: No
Enter number of process to modify it, or "done": [done]
Created file /home/oracle/dbvrep_google/dbvrep_google-APPLY.ddc.
Created file /home/oracle/dbvrep_google/dbvrep_google-MINE.ddc.
Created file /home/oracle/dbvrep_google/config/dbvrep_google-setup.dbvrep.
Created file /home/oracle/dbvrep_google/config/dbvrep_google-dbsetup_eleven_dbvrep.sql.
Created file /home/oracle/dbvrep_google/config/dbvrep_google-dbsetup_database_dbvrep_host_104.154.45.166_oracle.sql.
Created file /home/oracle/dbvrep_google/config/dbvrep_google-grants_eleven_dbvrep.sql.
Created file /home/oracle/dbvrep_google/config/dbvrep_google-grants_database_dbvrep_host_104.154.45.166_oracle.sql.
Created file /home/oracle/dbvrep_google/config/dbvrep_google-onetime.ddc.
Created file /home/oracle/dbvrep_google/start-console.sh.
Created file /home/oracle/dbvrep_google/dbvrep_google-run-dbvlin828.sh.
Created file /home/oracle/dbvrep_google/scripts/dbvrep_google-dbvlin828-start-MINE.sh.
Created file /home/oracle/dbvrep_google/scripts/dbvrep_google-dbvlin828-stop-MINE.sh.
Created file /home/oracle/dbvrep_google/scripts/dbvrep_google-dbvlin828-dbvrep-MINE.sh.
Created file /home/oracle/dbvrep_google/scripts/systemd-dbvrep-MINE_dbvrep_google.service.
Created file /home/oracle/dbvrep_google/scripts/upstart-dbvrep-MINE_dbvrep_google.conf.
Created file /home/oracle/dbvrep_google/scripts/dbvrep_google-dbvlin828-start-APPLY.sh.
Created file /home/oracle/dbvrep_google/scripts/dbvrep_google-dbvlin828-stop-APPLY.sh.
Created file /home/oracle/dbvrep_google/scripts/dbvrep_google-dbvlin828-dbvrep-APPLY.sh.
Created file /home/oracle/dbvrep_google/scripts/systemd-dbvrep-APPLY_dbvrep_google.service.
Created file /home/oracle/dbvrep_google/scripts/upstart-dbvrep-APPLY_dbvrep_google.conf.
Created file /home/oracle/dbvrep_google/Nextsteps.txt.
Created file /home/oracle/dbvrep_google/dbvrep_google-all.sh.
=====================================================================================================================================================================================================

Dbvisit Replicate wizard completed
Script /home/oracle/dbvrep_google/dbvrep_google-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]

 

Exit out of Dbvisit Replicate and start the script that has been generated by the setup wizard. These scripts configure the source and target databases for replication and create the dbvrep schema in Oracle and the dbvrep database in Google Cloud SQL (MySQL) database. Out of all these scripts, the only script that needs to be executed is <replication-name>-all.sh as this actually executes all the other scripts in the appropriate order. 

oracle@dbvlin828[/home/oracle/dbvrep_google]: ./dbvrep_google-all.sh
Setting up Dbvisit Replicate configuration
Configure database eleven...
This check fails if the DBID is not the expected one...

Ok, check passed.
Configure database database=dbvrep
ERROR 1044 (42000) at line 5: Access denied for user 'oracle'@'%' to database 'information_schema'
ERROR 1044 (42000) at line 6: Access denied for user 'oracle'@'%' to database 'information_schema'
Object grants for database eleven...
Object grants for database database=dbvrep
Setting up the configuration
Initializing......done
DDC loaded from database (0 variables).
Dbvisit Replicate version 2.8.00
Copyright (C) Dbvisit Software Limited.  All rights reserved.
DDC file /home/oracle/dbvrep_google/config/dbvrep_google-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> process 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>
dbvrep> # Configuring default processes
dbvrep> choose process MINE
Process type MINE set to: MINE.
dbvrep> choose process APPLY
Process type APPLY set to: APPLY.
dbvrep> PROCESS SWITCH_REDOLOG
Redo log switch requested.dbvrep> PROCESS SETUP MINE DROP DICTIONARY
0 dictionary objects dropped.
dbvrep> PROCESS SETUP MINE CREATE DICTIONARY
dbvrep> PROCESS SETUP MINE LOAD DICTIONARY
Oldest active transaction SCN: 5189815 (no active transaction)
Supplemental logging on database set.
Loading dictionary table DBRSCCOL$
Loading dictionary table DBRSCDEF$
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
dbvrep> PROCESS SETUP APPLY DROP DICTIONARY
0 dictionary objects dropped.
dbvrep> PROCESS SETUP APPLY CREATE DICTIONARY
dbvrep> PROCESS SETUP APPLY LOAD DICTIONARY
dbvrep> PROCESS SETUP PAIR MINE AND APPLY
Applier SCN set (start=5189825, current=5189825).
dbvrep> SET APPLY.INSTANTIATE_SCN NOW
Variable INSTANTIATE_SCN set to NOW for process APPLY.
dbvrep> SET MINE._PREPARE_SUPLOG_TYPE PK
Variable _PREPARE_SUPLOG_TYPE set to PK for process MINE.
dbvrep> EXCLUDE CREATE TABLE %.DBMS_TABCOMP_TEMP_UNCMP #Ignore tables
created by Compression Advisor
Exclude rule created.
dbvrep> EXCLUDE CREATE TABLE %.DBMS_TABCOMP_TEMP_CMP #Ignore tables
created by Compression Advisor
Exclude rule created.
dbvrep> EXCLUDE CREATE TABLE %.SCHEDULER$_% #Ignore tables created by
Oracle scheduler (also used by schema/full expdp/impdp)
Exclude rule created.
dbvrep> EXCLUDE CREATE TABLE %.CMP1$% #Ignore tables created by
Compression Advisor since 11.2.0.4
Exclude rule created.
dbvrep> EXCLUDE CREATE TABLE %.CMP2$% #Ignore tables created by
Compression Advisor since 11.2.0.4
Exclude rule created.
dbvrep> EXCLUDE CREATE TABLE %.CMP3$% #Ignore tables created by
Compression Advisor since 11.2.0.4
Exclude rule created.
dbvrep> EXCLUDE CREATE TABLE %.CMP4$% #Ignore tables created by
Compression Advisor since 11.2.0.4
Exclude rule created.
dbvrep> PROCESS SUPPLEMENTAL LOGGING TABLE "HR"."TEST1" ENABLE PRIMARY
KEY
dbvrep> PROCESS SUPPLEMENTAL LOGGING TABLE "HR"."TEST2" ENABLE PRIMARY
KEY
dbvrep> PROCESS SWITCH_REDOLOG
Redo log switch requested.dbvrep> PROCESS WAIT_SCN_FLIP
Waited 1 seconds until scn_to_timestamp changed.
dbvrep> #single-scn instantiation: lock all tables and schemas
dbvrep> PROCESS LOCK TABLES "HR"."TEST1" "HR"."TEST2"
Locking all tables.
Lock done.
dbvrep> #single-scn instantiation: unlock all tables and schemas, but
keep the SCN
dbvrep> PROCESS LOCK RELEASE LOCKS
dbvrep>
dbvrep> #prepare the tables (we use OFFLINE as neither MINE nor APPLY
is running; with OFFLINE we won't wait on network timeout)
dbvrep> PREPARE OFFLINE TABLE "HR"."TEST1"
Table HR.TEST1 instantiated at SCN 5192406
dbvrep> PREPARE OFFLINE TABLE "HR"."TEST2"
Table HR.TEST2 instantiated at SCN 5192406
dbvrep> #single-scn instantiation: unlock all tables and schemas,
forget the SCN (so it does not affect any further PREPARE statements)
dbvrep> PROCESS LOCK CLEAR SCN
dbvrep> PROCESS SWITCH_REDOLOG
Redo log switch requested.dbvrep> #prepare script for instantiation
dbvrep> create ddcdb from ddcfile
DDC loaded into database (394 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.
WARN-1850: No DDC DB available, dictionary table does not exist.
WARN-9247: Column HR.TEST1.TEST_FLOAT is of type FLOAT on mine, but
HR.TEST1.TEST_FLOAT is DOUBLE on apply.
WARN-9247: Column HR.TEST1.TEST_LONG is of type LONG on mine, but
HR.TEST1.TEST_LONG is TEXT on apply.
WARN-9247: Column HR.TEST1.TEST_NCHAR is of type NCHAR on mine, but
HR.TEST1.TEST_NCHAR is VARCHAR on apply.
WARN-9247: Column HR.TEST1.TEST_NVARCHAR2 is of type NVARCHAR2 on mine,
but HR.TEST1.TEST_NVARCHAR2 is VARCHAR on apply.
WARN-9247: Column HR.TEST1.TEST_RAW is of type RAW on mine, but
HR.TEST1.TEST_RAW is VARBINARY on apply.
WARN-9246: Column HR.TEST2.TEST_LONG_RAW is not in table HR.TEST2 on
apply.
WARN-9246: Column HR.TEST2.TEST_NUMBER is not in table HR.TEST2 on
apply.
WARN-9248: Column HR.TEST2.test_long_raw is not in table HR.TEST2 on
mine.
WARN-9248: Column HR.TEST2.test_number is not in table HR.TEST2 on
mine.
These steps are required after the dbvrep_google-all.sh script runs:

1) Create the necessary directory(ies) on the servers:
dbvlin823: /home/oracle/dbvrep_google
dbvlin828: /home/oracle/dbvrep_google

2) Copy the DDC files to the server(s) where the processes will run:
dbvlin823: /home/oracle/dbvrep_google/dbvrep_google-APPLY.ddc
dbvlin828: /home/oracle/dbvrep_google/dbvrep_google-MINE.ddc

3) Review that path to dbvrep executable is correct in the run scripts:
/home/oracle/dbvrep_google/dbvrep_google-run-dbvlin823.sh
/home/oracle/dbvrep_google/dbvrep_google-run-dbvlin828.sh

4) Copy the run script to the server(s) where the processes will run:
dbvlin823: /home/oracle/dbvrep_google/dbvrep_google-run-dbvlin823.sh
dbvlin828: /home/oracle/dbvrep_google/dbvrep_google-run-dbvlin828.sh


Starting the MINE and APPLY process requires their respective DDC config files and run scripts that actually starts these processes in background. ( On Windows system, MINE and APPLY act as services). These steps are outlined in Nextsteps.txt, but in the above example we copy dbvrep_google-APPLY.ddc and dbvrep_google-run-dbvlin823.sh to the server (target) and then start MINE and APPLY on source and target, respectively. 

Starting MINE on source

oracle@dbvlin828[/home/oracle/dbvrep_google]: ./dbvrep_google-run-dbvlin828.sh
Initializing......done
DDC loaded from database (394 variables).
Dbvisit Replicate version 2.8.00
Copyright (C) Dbvisit Software Limited.  All rights reserved.
DDC file /home/oracle/dbvrep_google/dbvrep_google-MINE.ddc loaded.
Starting process MINE...Created directory /home/oracle/dbvrep_google/mine/
started

The default transaction isolation level needs to be changed before starting the apply process. Execute following command in MySQL to set default transaction isolation level to READ-COMMITTED.

SET GLOBAL TRANSACTION ISOLATION LEVEL READ COMMITTED

 

Starting APPLY on target

oracle@dbvlin823[/home/oracle/dbvrep_google]: ./dbvrep_google-run-dbvlin823.sh
Initializing......done
DDC loaded from database (394 variables).
Dbvisit Replicate version 2.8.00
Copyright (C) Dbvisit Software Limited.  All rights reserved.
DDC file /home/oracle/dbvrep_google/dbvrep_google-APPLY.ddc loaded.
Starting process APPLY...Created directory /home/oracle/dbvrep_google/apply/
started

 

Dbvisit Replicate has now been configured and started in the background. To monitor replication progress start the console on source by executing start-console.sh script.

oracle@dbvlin828[/home/oracle/dbvrep_google]: ./start-console.sh
Initializing......done
DDC loaded from database (398 variables).
Dbvisit Replicate version 2.8.00
Copyright (C) Dbvisit Software Limited.  All rights reserved.
- Dbvisit Replicate 2.8.00(MAX edition) - Evaluation License expires in 30 days
MINE is running. Currently at plog 2375 and SCN 5194352 (01/21/2016 14:08:47).
APPLY is running, initialization NOT yet complete. Currently at plog 2370 and SCN ....
Progress of replication dbvrep_google:MINE->APPLY: total/this execution

 

When starting the MINE and APPLY processes for the first time they enter the INITIALIZATION state. In this phase Dbvisit Replicate replicates the contents of its internal dictionary and repository from the source to the target database. To monitor the progress of initialization, the LIST PROGRESS ALL command can be used.

Replication proper does not commence until the initialization phase has been completed. This is completed when the console show both MINE and APPLY are running, as per the following:

MINE IS running. Currently at plog 2378 and SCN 5197352 (1/21/2016 15:26:17).
APPLY IS running. Currently at plog 2378 and SCN 5197051 (1/21/2016 15:26:13).

 

Now, all insert, update and delete operations on the HR.TEST1 and HR.TEST2 tables in Oracle will be replicated to the HR.TEST1 and HR.TEST2 tables in Google Cloud SQL (MySQL).

  • Database and table names are case sensitive in MySQL (Google Cloud SQL)
  • Scripts generated by setup wizard contains plain text passwords. You can delete these scripts once replication is configured and running.