Oracle GoldenGate: Migrate to Microservices Architecture

Introduction

Oracle GoldenGate Microservices Architecture (OGG-MA) is a Restful API microservices based architecture that provides functionality for the configuration, installation, and management of Oracle GoldenGate services using a web-based user interface. In this article, we’ll migrate an existing Oracle GoldenGate Classic (OGG) instance to an OGG-MA deployment.

The concepts, scripts, and information presented in this article are for educational purposes only. They are not supported by Oracle Development or Support, and come with no guarantee or warrant for functionality in any environment other than the test system used to prepare this article. Before applying any changes presented in this article to your environment, you should thoroughly test to assess functionality and performance implications.

Main Article

My source and target databases are Oracle multi-tenant databases running on a single database server, a Kafka target server, and a Hadoop target server. As a pre-requisite for migrating to OGG-MA, I installed the most recent Oracle Database PSU to ensure the database and pluggable databases were up to date with security and priority fixes.

The figure below depicts the existing OGG replication environment:

oggma16

These are the OGG Groups that will be migrated to OGG-MA:

GGSCI (centos0ra12) 1> status all
Program     Status      Group       Lag at Chkpt  Time Since Chkpt
MANAGER     RUNNING
EXTRACT     RUNNING     EPDBORCL    00:00:10      00:00:06
Description “Integrated Extract – PDBORCL source”
EXTRACT     RUNNING     P_HADP      00:00:00      00:00:09
Description “Extract Data Pump – OGGBD Hadoop”
EXTRACT     RUNNING     P_KFKA      00:00:00      00:00:00
Description “Extract Data Pump – OGGBD Kafka”
REPLICAT    RUNNING     R_DW        00:00:00      00:00:01
Description “Integrated Replicat – PDBNOREAST target”
REPLICAT    RUNNING     R_RPTG      00:00:49      00:06:04
Description “Integrated Replicat – PDBWEST target”

The installation of the OGG-MA software is detailed in the Oracle GoldenGate documentation, so we are not covering that in this article. For this migration I installed OGG-MA on the same server as the existing OGG instance at the disk location /u01/oracle/app/goldengate/oggma123 (I could have installed OGG-MA on a dedicated mid-tier server and migrated to remote capture and apply as well).

Create Deployment

After installing the OGG-MA software, run the $OGG_HOME/bin/oggca.sh script to create a deployment for this new Oracle GoldenGate instance. Deployment creation is detailed in the Oracle GoldenGate documentation.

Once the deployment is created, login to the Admin Server and access the Configuration menu. In the Database pane, we’ll enter the existing database access credentials used for data capture and data apply.

Root Container Credentials

Provide the database credential used by Integrated Extract for data capture.

oggma1

Test by logging into the database.

oggma2

oggma3

Log out of the database after validating the credentials.

Target Pluggable Database Credentials

Provide the credentials for data apply in each target pluggable database and test each connection.

oggma4

After I added all of the database credentials, my web page looks like this:

oggma5

Parameter Files

We need to integrated our old OGG Classic parameter settings into the new OGG-MA deployment.

GLOBALS

When the deployment was provisioned, a default GLOBALS file was created. For my test system, the location for this file is /u01/oracle/app/goldengate/deployments/centosOra12/etc/conf/ogg:

oggma6My existing OGG instance contains a GLOBALS file with the following settings:

ggschema ggadmin

— Suppress duplicate info and warning messages in report file
nodupmsgsuppression

— Create trail and discard files with permissions: -rw-rw—-
outputfileumask 007

— Only send warning and error messages to the system log
syslog warn, error

To merge this file with the OGG-MA deployment GLOBALS file, open both files with a text editor. Copy and paste the settings from the old file into the new file. My OGG-MA deployment GLOBALS file now looks like this:

ggschema ggadmin

— LJP: Merged from OGG Classic instance

— Suppress duplicate info and warning messages in report file
nodupmsgsuppression

— Create trail and discard files with permissions: -rw-rw—-
outputfileumask 007

— Only send warning and error messages to the system log (deprecated in OGG 12.3)
–syslog warn, error

Save the edits and close both files.

Integrated Extract Parameter File

Copy the Integrated Extract parameter file from the [OGG Classic]/dirprm directory to the [deployment]/etc/conf/ogg directory. In my test environment, OGG Classic is installed at /u01/oracle/app/goldengate/ogg122 and my Integrated Extract parameter file is epdborcl.prm. This file is copied into my OGG-MA configuration directory at /u01/oracle/app/goldengate/deployments/centosOra12/etc/conf/ogg.

oggma8

Edit the Integrated Extract parameter file to (1) include the database credentials we setup previously for data capture and (2) remove the directory location for the EXTTRAIL (by default all trails are located in the [deployment]/var/lib/data directory, /u01/oracle/app/goldengate/deployments/centosOra12/var/lib/data in my test environment). After making these edits, my Integrated Extract parameter file looks like this:

extract epdborcl
— Credentials for database capture

useridalias ggroot domain orcl
exttrail ea
reportcount every 20 minutes, rate
reportrollover at 00:01
report at 00:01
statoptions resetreportstats
ddl include mapped
ddloptions report
warnlongtrans 15m, checkinterval 15m
table pdborcl.tpc.*;

Integrated Replicat Parameter Files

Copy the Integrated Replicat parameter files from the [OGG Classic]/dirprm directory to the [deployment]/etc/conf/ogg directory. In my OGG Classic instance, there are two Integrated Replicats; R_DW and R_RPTG. After copying the files to the OGG-MA deployment location, edit each file to include the database credentials previously defined for data apply.

oggma9

After making the edits, my parameter files look like this:

replicat r_dw
useridalias ggapply domain pdbnoreast
reportcount every 20 minutes, rate
reportrollover at 00:01
report at 00:01
statoptions resetreportstats
ddl include mapped
ddloptions report
map pdborcl.tpc.*, target pdbnoreast.tpc.*;

replicat r_rptg
useridalias ggapply domain pdbwest
reportcount every 20 minutes, rate
reportrollover at 00:01
report at 00:01
statoptions resetreportstats
ignoredeletes
map pdborcl.tpc.orders_products, target pdbwest.tpcrpt.reporting_products,
colmap (usedefaults,
line_id = orders_products_id
)
;
map pdborcl.tpc.customers_info, target pdbwest.tpcrpt.reporting_customers,
colmap (usedefaults,
customers_id = customers_info_id,
customers_last_logon = customers_info_last_logon,
customers_created_ts = customers_info_created_ts,
customers_last_modified = customers_info_last_modified
);
map pdborcl.tpc.orders, target pdbwest.tpcrpt.reporting_orders;

Extract Data Pumps

The two Extract Data Pumps, P_KFKA and P_HADP, cannot be migrated to OGG-MA as data pump functionality has been deprecated and replaced by Distribution Paths. We’ll discuss how to get data over to the Kafka and Hadoop OGG Classic instances a little later in the article.

Migrate OGG

We’re now ready to start the migration from OGG Classic to OGG-MA.

Environment Variables

The OGG_HOME environment variable must reference the location where the OGG-MA software was installed. The OGG_ETC_HOME and OGG_VAR_HOME variables must reference the deployment directory locations.

[oracle@centos0ra12 ~]$ echo $OGG_HOME
/u01/oracle/app/goldengate/ogg123ma
[oracle@centos0ra12 ~]$ echo $OGG_VAR_HOME
/u01/oracle/app/goldengate/deployments/var
[oracle@centos0ra12 ~]$ echo $OGG_ETC_HOME
/u01/oracle/app/goldengate/deployments/etc

Connect To Service Manager

Go to the $OGG_HOME/bin directory and execute the adminclient program.

[oracle@centos0ra12 ~]$ cd $OGG_HOME/bin
[oracle@centos0ra12 bin]$ ./adminclient
Oracle GoldenGate Administration Client for Oracle
Version 12.3.0.1.2 OGGCORE_12.3.0.1.0_PLATFORMS_171208.0005

Copyright (C) 1995, 2017, Oracle and/or its affiliates. All rights reserved.

Linux, x64, 64bit (optimized) on Dec  8 2017 07:43:27
Operating system character set identified as UTF-8.

OGG (not connected) 1>

Establish a connection to the Service Manager. The syntax for this command is connect http[s]://[node]:[service manager port] as [user] [!]

;where:

http[s]: defines the connection type; secure or unsecure. OGG-MA QA and Production environments should have a valid and properly trusted SSL certificate issued by a Certificate Authority installed to ensure secure communication protocols are used for connections and data transfer. Development, unit testing and other environments may use a self-signed SSL certificate or may be setup as non-secure (not a best practice).

[node]: is the Service Manager address defined during deployment provisioning.

[service manager port]: is the Service Manager port defined during deployment provisioning.

[user]: is the Service Manager user defined during deployment provisioning.

[!]: is used to establish an https connection to Service Manager when a self-signed SSL certificate is installed on the server.

OGG (not connected) 1> connect http://centosOra12:17000 as oracle
Password for ‘oracle’ at ‘http://centosora12:17000’:
Using default deployment ‘centosOra12’

OGG (http://centosora12:17000 centosOra12) 2>

(Note: My sandbox server does not have a SSL certificate installed, so the connection to Service Manager is unsecure. This is not best practice.)

Integrated Extract

Go to the OGG Classic instance and start GGSCI. Shutdown the Integrated Extract.

Be sure to check for long running transactions against tables being captured by OGG. These transactions must commit or be rolled back before shutting down Integrated Extract. Failing to do this will result in data inconsistencies in all downstream replication environments.

GGSCI (centos0ra12) 10> stop epdborcl

Sending STOP request to EXTRACT EPDBORCL …
Request processed.

Execute the GGSCI INFO command and get the Integrated Extract Log Read Checkpoint SCN.

GGSCI (centos0ra12) 11> info epdborcl

EXTRACT    EPDBORCL  Last Started 2018-04-25 08:13   Status STOPPED
Description          “Integrated Extract – PDBORCL source”
Checkpoint Lag       00:00:01 (updated 00:05:14 ago)
Log Read Checkpoint  Oracle Integrated Redo Logs
2018-04-25 08:54:23
SCN 0.54188096 (54188096)

Add the Integrated Extract to the OGG-MA deployment via the adminclient.

First use the DBLOGIN command to establish a connection to the source database:

OGG (http://centosora12:17000 centosOra12) 4> dblogin useridalias ggroot domain orcl
Successfully logged into database.

Use the ADD EXTRACT command, specifying the SCN recorded from the OGG Classic instance:

OGG (http://centosora12:17000 centosOra12 as ggroot) 5> add extract epdborcl integrated tranlog scn 54188096
2018-04-25T13:14:38Z  INFO    OGG-08100  EXTRACT (Integrated) added.
2018-04-25T13:14:38Z  INFO    OGG-08100  EXTRACT altered.

Us the ADD EXTTRAIL command to add this Integrated Extract’s Trail:

OGG (http://centosora12:17000 centosOra12 as ggroot) 7> add exttrail ea, extract epdborcl, megabytes 1000
2018-04-25T13:19:42Z  INFO    OGG-08100  EXTTRAIL added.

Start the Integrated Extract:

OGG (http://centosora12:17000 centosOra12 as ggroot) 8> start extract epdborcl
2018-04-25T13:20:43Z  INFO    OGG-00975  EXTRACT EPDBORCL starting
2018-04-25T13:20:43Z  INFO    OGG-15426  EXTRACT EPDBORCL started

Check the Integrated Extract status:

OGG (http://centosora12:17000 centosOra12 as ggroot) 17> info extract epdborcl

EXTRACT    EPDBORCL  Last Started 2018-04-25 09:23   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:10 ago)
Process ID           10291
Log Read Checkpoint  Oracle Integrated Redo Logs
First Record
SCN 0.54188096 (54188096)

Or from the Service Manager GUI:

oggma10

Integrated Replicat

Before shutting down the Integrated Replicats in the OGG Classic instance, ensure all queued OGG Trail data has been applied to the target.

Execute the GGSCI INFO command to get the last read position of each Integrated Replicat:

GGSCI (centos0ra12) 7> info r*

REPLICAT   R_DW      Last Started 2018-04-25 08:13   Status RUNNING
Description          “Integrated Replicat – PDBNOREAST target”
Checkpoint Lag       00:00:00 (updated 00:00:01 ago)
Process ID           4633
Log Read Checkpoint  File ./dirdat/ea000000006
2018-04-25 08:54:23.000000  RBA 14903502

REPLICAT   R_RPTG    Last Started 2018-04-25 09:38   Status RUNNING
Description          “Integrated Replicat – PDBWEST target”
INTEGRATED
Checkpoint Lag       00:00:00 (updated 00:00:05 ago)
Process ID           11537
Log Read Checkpoint  File ./dirdat/ea000000006
2018-04-25 09:35:05.403993  RBA 14903502

Check the number and size of OGG Trails remaining to be processed on disk:

GGSCI (centos0ra12) 10> shell ls -l ./dirdat/ea*

-rw-r—–. 1 oracle oracle 873864694 Apr 23 08:39 ./dirdat/ea000000002
-rw-r—–. 1 oracle oracle  21148778 Apr 23 11:03 ./dirdat/ea000000003
-rw-r—–. 1 oracle oracle      1478 Apr 24 08:12 ./dirdat/ea000000004
-rw-r—–. 1 oracle oracle      1478 Apr 25 08:13 ./dirdat/ea000000005
-rw-rw—-. 1 oracle oracle  14903502 Apr 25 08:54 ./dirdat/ea000000006

If the RBA value of the Integrated Replicat Log Read Checkpoint matches the file size value from the output of the ls command; there is no more data to be processed. The Integrated Replicats may be shutdown.

GGSCI (centos0ra12) 11> stop r*

Sending STOP request to REPLICAT R_DW …
Request processed.

Sending STOP request to REPLICAT R_RPTG …
Request processed.

Add the Integrated Replicats to the OGG-MA deployment. For each, use the DBLOGIN adminclient command to establish a connection to the respective target database and then use the ADD REPLICAT adminclient command to add the Integrated Replicat.

OGG (http://centosora12:17000 centosOra12 as ggroot) 18> dblogin useridalias ggapply domain pdbnoreast
Successfully logged into database.

OGG (http://centosora12:17000 centosOra12 as ggapply) 19> add replicat r_dw integrated exttrail ea checkpointtable pdbnoreast.ggadmin.ggchkpt
2018-04-25T13:53:07Z  INFO    OGG-08100  REPLICAT (Integrated) added.

OGG (http://centosora12:17000 centosOra12 as ggapply) 20> dblogin useridalias ggapply domain pdbwest
Successfully logged into database.

OGG (http://centosora12:17000 centosOra12 as ggapply) 21> add replicat r_rptg integrated exttrail ea checkpointtable pdbwest.ggadmin.ggcheckpoint
2018-04-25T13:54:26Z  INFO    OGG-08100  REPLICAT (Integrated) added.

Start the Integrated Replicats.

OGG (http://centosora12:17000 centosOra12 as ggapply) 22> start replicat r_dw
2018-04-25T13:55:41Z  INFO    OGG-00975  REPLICAT R_DW starting
2018-04-25T13:55:41Z  INFO    OGG-15426  REPLICAT R_DW started

OGG (http://centosora12:17000 centosOra12 as ggapply) 23> start replicat r_rptg
2018-04-25T13:55:46Z  INFO    OGG-00975  REPLICAT R_RPTG starting
2018-04-25T13:55:46Z  INFO    OGG-15426  REPLICAT R_RPTG started

Check their status:

OGG (http://centosora12:17000 centosOra12 as ggapply) 24> info r_dw

REPLICAT   R_DW      Last Started 2018-04-25 09:55   Status RUNNING
INTEGRATED
Checkpoint Lag       01:02:27 (updated 00:00:27 ago)
Process ID           12827
Log Read Checkpoint  File /u01/oracle/app/goldengate/deployments/centosOra12/var/lib/data/ea000000000
2018-04-25 08:54:23.000000  RBA 7544

OGG (http://centosora12:17000 centosOra12 as ggapply) 25> info r_rptg

REPLICAT   R_RPTG    Last Started 2018-04-25 09:55   Status RUNNING
INTEGRATED
Checkpoint Lag       01:02:14 (updated 00:00:51 ago)
Process ID           12838
Log Read Checkpoint  File /u01/oracle/app/goldengate/deployments/centosOra12/var/lib/data/ea000000000
2018-04-25 08:54:23.000000  RBA 3053

Or from the Service Manager GUI:

oggma11

Extract Data Pumps

Before shutting down the Extract Data Pumps, ensure all queued OGG Trail data has been shipped to the target OGG instances.

Execute the GGSCI INFO command to get the last read position of each Extract Data Pump:

GGSCI (centos0ra12) 18> info p*

EXTRACT    P_HADP    Last Started 2018-04-25 08:12   Status RUNNING
Description          “Extract Data Pump – OGGBD Hadoop”
Checkpoint Lag       00:00:00 (updated 00:00:07 ago)
Process ID           4625
Log Read Checkpoint  File ./dirdat/ea000000006
2018-04-25 08:54:23.000000  RBA 14903502

EXTRACT    P_KFKA    Last Started 2018-04-25 08:12   Status RUNNING
Description          “Extract Data Pump – OGGBD Kafka”
Checkpoint Lag       00:00:00 (updated 00:00:00 ago)
Process ID           4626
Log Read Checkpoint  File ./dirdat/ea000000006
2018-04-25 08:54:23.000000  RBA 14903502

Check the number and size of OGG Trails remaining to be processed on disk:

GGSCI (centos0ra12) 19> shell ls -l ./dirdat/ea*

-rw-r—–. 1 oracle oracle 873864694 Apr 23 08:39 ./dirdat/ea000000002
-rw-r—–. 1 oracle oracle  21148778 Apr 23 11:03 ./dirdat/ea000000003
-rw-r—–. 1 oracle oracle      1478 Apr 24 08:12 ./dirdat/ea000000004
-rw-r—–. 1 oracle oracle      1478 Apr 25 08:13 ./dirdat/ea000000005
-rw-rw—-. 1 oracle oracle  14903502 Apr 25 08:54 ./dirdat/ea000000006

If the RBA value of the Extract Data Pump Log Read Checkpoint matches the file size value from the output of the ls command; there is no more data to be processed. The Extract Data Pumps may be shutdown.

GGSCI (centos0ra12) 19> stop p*

Sending STOP request to EXTRACT P_HADP …
Request processed.

Sending STOP request to EXTRACT P_KFKA …
Request processed.

As mentioned previously, Extract Data Pump functionality has been deprecated in OGG-MA. Instead data is transmitted to remote OGG-MA deployments or OGG 12.3 Classic instances via Distribution Paths. My target OGG instances are running OGG for Big Data version 12.3.1, so I may setup a path to each instance via the adminclient ADD DISTPATH command:

OGG (http://centosora12:17000 centosOra12) 33> add distpath pkafka source trail://centosOra12:17101/services/v2/sources?trail=ea target ogg://kafka:15000/services/v2/targets?trail=dirdat/kf targettype manager
2018-04-25T14:54:26Z  INFO    OGG-08511  The path ‘pkafka’ has been added.

OGG (http://centosora12:17000 centosOra12) 34> add distpath phadp source trail://centosOra12:17101/services/v2/sources?trail=ea target ogg://hadp:15000/services/v2/targets?trail=dirdat/pd targettype manager
2018-04-25T14:54:42Z  INFO    OGG-08511  The path ‘phadp’ has been added.

For OGG 12.3 Classic targets, the syntax of the add distpath command is:

add distpath [path name] source trail://[node]:[port]/services/v2/sources?trail=[trail name] target ogg://[node]:[OGG manager port]/services/v2/targets?trail=[trail location/name] targettype manager

For more information on the ADD DISTPATH command, see the Oracle GoldenGate Admin Client Commands section of the Oracle GoldenGate Reference Guide.

Start each Distribution Path:

OGG (http://centosora12:17000 centosOra12) 36> start distpath pkafka
2018-04-25T15:17:19Z  INFO    OGG-08513  The path ‘pkafka’ has been started.

OGG (http://centosora12:17000 centosOra12) 37> start distpath phadp
2018-04-25T15:17:35Z  INFO    OGG-08513  The path ‘phadp’ has been started.

Check the status of the Distribution Paths:

OGG (http://centosora12:17000 centosOra12 as ggapply) 38> info distpath pkafka

Path Name: pkafka
Status: running
Source URI: trail://centosOra12:17101/services/v2/sources?trail=ea
Target URI: ogg://kafka:15000/services/v2/targets?trail=dirdat/kf

OGG (http://centosora12:17000 centosOra12 as ggapply) 39> info distpath phadp

Path Name: phadp
Status: running
Source URI: trail://centosOra12:17101/services/v2/sources?trail=ea
Target URI: ogg://hadp:15000/services/v2/targets?trail=dirdat/pd

Or you may login to the Distribution Server via a web browser:

oggma12

In each target OGG instance, ensure all queued OGG Trail data has been applied by Replicat, stop the Replicat, and alter it to begin reading the new Trail created via the Distribution Path:

GGSCI (kafka-0.localdomain) 2> info rkafka

REPLICAT   RKAFKA    Last Started 2018-04-25 08:09   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:07 ago)
Process ID           3695
Log Read Checkpoint  File /u01/OGG123BD/dirdat/oa000000000
2018-04-11 13:04:23.938396  RBA 1196745

GGSCI (kafka-0.localdomain) 3> shell ls -l ./dirdat/oa*

-rw-r—–. 1 oracle oracle 1196745 Apr 11 13:04 ./dirdat/oa000000000

GGSCI (kafka-0.localdomain) 4> stop rkafka

Sending STOP request to REPLICAT RKAFKA …
Request processed.

GGSCI (kafka-0.localdomain) 5> alter rkafka, exttrail ./dirdat/kf

REPLICAT altered.

GGSCI (kafka-0.localdomain) 6> start rkafka

Sending START request to MANAGER …
REPLICAT RKAFKA starting

GGSCI (kafka-0.localdomain) 7> info rkafka

REPLICAT   RKAFKA    Last Started 2018-04-25 11:27   Status RUNNING
Checkpoint Lag       02:30:45 (updated 00:00:00 ago)
Process ID           15756
Log Read Checkpoint  File /u01/OGG123BD/dirdat/kf000000000
2018-04-25 08:57:19.000027  RBA 201375299

GGSCI (hadp) 2> info rhadp

REPLICAT   RHADP     Last Started 2018-04-25 08:12   Status RUNNING
Checkpoint Lag       00:00:00 (updated 00:00:01 ago)
Process ID           3469
Log Read Checkpoint  File /u01/goldengate/ogg12301BD/dirdat/hd000000024
2018-04-25 08:54:23.567892  RBA 7944761

GGSCI (hadp) 3> shell ls -l ./dirdat/hd*

-rw-r—–. 1 Oracle Oracle 7944761 Apr 25 08:54 ./dirdat/hd000000024

GGSCI (hadp) 4> stop rhadp

Sending STOP request to REPLICAT RHADP …
Request processed.

GGSCI (hadp) 5> alter rhadp, exttrail ./dirdat/pd

REPLICAT altered.

GGSCI (hadp) 6> start rhadp

Sending START request to MANAGER …
REPLICAT RHADP starting

GGSCI (hadp) 7> info rhadp

REPLICAT   RHADP     Last Started 2018-04-25 11:31   Status RUNNING
Checkpoint Lag       02:35:26 (updated 00:00:00 ago)
Process ID           5000
Log Read Checkpoint  File /u01/goldengate/ogg12301BD/dirdat/pd000000000
2018-04-25 08:56:38.850010  RBA 154015001

Scripting Commands

All of the adminclient commands I executed above could have been executed via an obey file instead of typing each one at the command line.

OGG (http://centosora12:17000 centosOra12 as ggapply) 40> help obey

OBEY

Syntax: OBEY <file-name>

Use OBEY to process a file that contains a list of Oracle GoldenGate commands.
OBEY is useful for executing commands that are frequently used in sequence.

Example 1

OBEY ./mycommands.txt

The preceding command executes a file that looks similar to the following example:

dblogin useridalias ggroot domain orcl
add extract epdborcl integrated tranlog scn 54188096
add exttrail ea, extract epdborcl, megabytes 1000
dblogin useridalias ggapply domain pdbnoreast
add replicat r_dw integrated exttrail ea checkpointtable pdbnoreast.ggadmin.ggchkpt
dblogin useridalias ggapply domain pdbwest
add replicat r_rptg integrated exttrail ea checkpointtable pdbwest.ggadmin.ggcheckpoint
add distpath pkafka source trail://centosOra12:17101/services/v2/sources?trail=ea target ogg://kafka:15000/services/v2/targets?trail=dirdat/kf targettype manager
add distpath phadp source trail://centosOra12:17101/services/v2/sources?trail=ea target ogg://hadp:15000/services/v2/targets?trail=dirdat/pd targettype manager
start extract epdborcl
start replicat r_dw
start replicat r_rptg
start distpath pkafka
start distpath phadp

Post Migration

The migration is now complete, stop the OGG Classic Manager.

GGSCI (centos0ra12) 20> stop mgr !

Sending STOP request to MANAGER …
Request processed.
Manager stopped.

Enable housekeeping in the OGG-MA deployment so fully consumed Extract Trails are purged.

In the Admin Server GUI, open the Configuration screen, select the Maintenance pane, and the Purge Trails option.

oggma13

Select the + and fill in the information to create a new Purge Trails Task.

oggma14aSelect the Submit button to complete the process.

oggma15

 

Summary

In this article we demonstrated the migration of an Oracle GoldenGate Classic instance to the new Oracle Microservices Architecture.

For more information on what other articles are available for Oracle GoldenGate please view our index page.

Add Your Comment