Oracle GoldenGate Veridata – How to move or migrate repository configuration to another server

Introduction

This document will walk you through how to move or migrate the Veridata configuration or repository to another server in a Linux environment. The migration of the Veridata configuration can be done on any platform supported by Veridata, however this document is for Linux only.

Main Article

The example configuration in this document was done using 2 separate Linux servers. The 1st Veridata server (ole-veridata-old) which contains the Veridata configuration that will be migrated and the 2nd Veridata server (ole-veridata-new) where the configuration will be migrated or moved to.

Prerequisites

Source Configuration (Old) Veridata Server (ole-veridata-old)

Software and Platform Requirements:

  • 64 bit Redhat/OEL x86 Linux
  • Java v6
  • Oracle 11g or above database for Veridata Repository
  • Oracle GoldenGate Veridata Server 11.2.x for Linux-x86

Target Configuration (New) Veridata Server (ole-veridata-new)

Software and Platform Requirements:

  • 64 bit Redhat/OEL x86 Linux
  • Java v6
  • Oracle 11g or above database for Veridata Repository
  • Oracle GoldenGate Veridata Server 11.2.x for Linux-x86

 

Veridata Architecture

Veridata Overview Diagram

veridata_migration_01

Veridata Configuration Migration Steps & Procedure

Veridata Source Configuration Server (ole-veridata-old)

1. Shutdown Veridata server process if it’s running.

Shell> ./web/bin/shutdown.sh

veridata_migration_02

2. Create an Export File of the Veridata Repository (Schema) using Oracle’s Export/Import Dump Utility

a. Make sure you have the necessary exp/imp directory defined in the Oracle database and that you can do this using sqlplus

Sqlplus> conn / as sysdba;
Sqlplus> create or replace directory veridata_dump as ‘/home/oracle/ogg/veridata_dump’;

veridata_migration_03

b. Export the Veridata Repository using the expdp utility.

Shell> expdp system/oracle schemas=VERIDATA directory=veridata_dump dumpfile=veridata_all.dmp logfile=expdpVERIDATA_all.log

veridata_migration_04

c. Backup the Veridata ./shared/data directory using tar or zip

Shell> tar cvf vd_shared_data_dir.tar shared/data

d. Copy the export dump file (veridata_all.dmp) and the backup configuration tar file (vd_shared_data_dir.tar) onto the new server using scp or whatever utility you’re comfortable using.

Shell> scp vd_shared_data_dir.tar ole-veridata-new:/home/oracle/ogg/veridata_v112100

veridata_migration_05

Shell> scp veridata_all.dmp ole-veridata-new:/home/oracle/ogg/veridata_dump

veridata_migration_06

Veridata Target Configuration Server (ole-veridata-new)

Note: If you haven’t installed Veridata Server Software on the new server you may want to review ”Installing Veridata using Oracle as Repository” – http://docs.oracle.com/cd/E35209_01/doc.1121/e29092/install_using_oracle.htm#g1008410

3. Shutdown Veridata server if it’s running.

Shell> ./web/bin/shutdown.sh

veridata_migration_07

4. Import the Veridata dump file that was taken from the Veridata Source Server (ole-veridata-old) using Oracle’s Import Dump Utility

a. Make sure you have the necessary exp/imp directory defined in the Oracle database and that you can do this using sqlplus

Sqlplus> conn / as sysdba;
Sqlplus> create or replace directory veridata_dump as ‘/home/oracle/ogg/veridata_dump’;

veridata_migration_08

b. Run Oracle’s import dump utility to migrate the Veridata schema into the new Veridata server with “replace” function enabled against the dump file (veridata_all.dmp)

Shell> impdp system/oracle schemas=VERIDATA directory=veridata_dump table_exists_action=replace dumpfile=veridata_all.dmp

veridata_migration_09

5. Extract the backup configuration tar file (vd_shared_data_dir.tar) onto the Veridata Home directory using tar utility

Shell> tar xvf vd_shared_data_dir.tar

veridata_migration_10

At this point you are now ready to start the Veridata server and verify that you can access the configuration that you have migrated into the new Veridata server using the Veridata web user interface (UI).

a. Start the Veridata server using startup.sh script

Shell> ./web/bin/startup.sh

veridata_migration_11

b. Verify the configuration to be sure everything from the repository was successfully migrated using the web user interface. Check the Home, Connection, Group, Job and profile configuration screens in the UI and validate that everything has been migrated.

HOME SCREEN:

veridata_migration_12

CONNECTION CONFIGURATION SCREEN:

veridata_migration_13

GROUP CONFIGURATION SCREEN:

veridata_migration_14

JOB CONFIGURATION SCREEN:

veridata_migration_15

PROFILE CONFIGURATION SCREEN:

veridata_migration_16

That’s all there is, now you are ready to start running jobs on the new Veridata Server.

Add Your Comment