Oracle Goldengate Extract, Pump, and Replicat

-
This is just a quick demonstration of setting up extract, pump, and replicate.

I prefer to edit the prm files at OS level, but we can also do

GGSCI> edit param esource

to enter the vi mode to create the prm file.

Here are the sample prm files used in the demonstration:
prm files:
--------------------------------
Source: (2 processes)
~~~~~~~~~~~~~~~~
esource.prm
~~~~~~~~~
EXTRACT ESOURCE

SETENV (ORACLE_SID=source)
SETENV (ORACLE_HOME="/source/app/oracle/product/11.2.0.3")

userid ggg, password ggg

EXTTRAIL /ggSource/app/goldengate/product/12.1.0/dirdat/es

--Resolves the TABLES to be replicated when they first encounter a dml operation
WILDCARDRESOLVE DYNAMIC

--Reduce the system I/O overhead of redolog reads
EOFDELAY 5

TABLE mine.table;


psource.prm
~~~~~~~~~
EXTRACT PDWDSPRD

SETENV (ORACLE_SID=source)
SETENV (ORACLE_HOME="/source/app/oracle/product/11.2.0.3")

userid ggg, password ggg

RMTHOST targetServer.example.net, MGRPORT 7809
RMTTRAIL /ggTarget/app/goldengate/product/12.1.0/dirdat/se

TABLE mine.table;


Target: (1 process)
~~~~~~~~~~~~~~
rtarget.prm
~~~~~~~~
REPLICAT RTARGET

SETENV (ORACLE_SID=target)
SETENV (ORACLE_HOME="/target/app/oracle/product/11.2.0/dbhome_1")

userid ggg, password ggg
REPERROR (1403, IGNORE)
WILDCARDRESOLVE DYNAMIC
HANDLECOLLISIONS
ASSUMETARGETDEFS
MAP mine.table, TARGET yours.table;




at source:

$ ./ggsci

GGSCI> dblogin userid ggg, password ggg

GGSCI> add extract esource, tranlog, begin now

GGSCI> add exttrail /ggSource/app/goldengate/product/12.1.0/dirdat/es, extract esource

GGSCI> add extract psource, exttrailsource /ggSource/app/goldengate/product/12.1.0/dirdat/es, begin now

GGSCI> add rmttrail /ggTarget/app/goldengate/product/12.1.0/dirdat/se, extract psource

GGSCI> start esource

GGSCI> start psource

GGSCI> info all

MANAGER     RUNNING
EXTRACT     RUNNING     ESOURCE     00:00:00      00:00:05
EXTRACT     RUNNING     PSOURCE    00:00:00      00:00:06



at target:

$ ./ggsci

GGSCI> dblogin userid ggg, password ggg

GGSCI> add checkpointtable ggg.checkpoint

GGSCI> add replicat rtarget exttrail /ggTarget/app/goldengate/product/12.1.0/dirdat/se, checkpointtable ggg.checkpoint

GGSCI> start rtarget

GGSCI> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
REPLICAT    RUNNING     RTARGET    00:00:03      00:00:03




Comments

  1. SwimHealth NetworkApril 14, 2022 at 12:03 PM

    Thanks for the great blog. You might have Suffered from fever since your childhood but not aware of why fever come and why it repeats. Well, I have seen some tips out there you can also check.

    ReplyDelete

Post a Comment

Popular posts from this blog

MongoDB tip: 4 ways to modify replica set configuration

-
This is just a quick guide on how to modify your replica set settings in 4 different ways. This guide is assuming you have a functional replica set ready, it doesn't matter if it's a single node or multi-node replica set. In each of the four method, I am looking to modify the priority of the _id=0 node Method 1: Via Mongo Shell Login to your Mongo shell,  simply type in mongo , assuming default port is being used and authentication is not enabled [in Mongo shell] cfg = rs.conf() cfg.members[0].priority=99 rs.reconfig(cfg) # "ok":1 indicates the new configuration has been set  MongoDB Enterprise minvera:PRIMARY> rs.reconfig(cfg) {         "ok" : 1,         "operationTime" : Timestamp(1528464949, 1),         "$clusterTime" : {                 "clusterTime" : Timestamp(1528464949, 1),                 "signature" : {                         "hash" : BinData(0
Read more

MongoDB Quick Note: BI Connector Issue

-
This is just a quick note of what can stop mongosqld from working properly that I wasn't aware of. Background: My work runs everything mongodb inside of docker containers, so sometimes it's not as straight forward to see immediately of what's preventing your container from working properly What happened: I ran into issue that my container does not stay up after I updated my drdl to reflect new fields introduced to the underlying collection. How to debug: Go to the host server, copy out entrypoint.sh and add sleep 100000000 to before mongosqld is executed. This force the container to stay up for us to look into issue. Cause of the issue: When I updated the drdl, I used tab instead of space, which is causing the mongsqld to error out Fix: Just replace tab with space and everything is back to normal
Read more

MongoDB Tips: Kill long running processes

-
This is just a quick and simple script to find all active opid that has been running over 10 seconds and they are running against the databases and collections you can specify in the "ns" filter. It's best to first run db.currentOp(    {      "active" : true,      "secs_running" : { "$gt" : 10 },      "ns" : {$in:["equipment.detachment","personnel.detail","personnel.unavailability","personnel.detachment"]}    } ).inprog.forEach(function (doc) { print(doc.opid); }) and verify your output before you execute the kill command in my experience to make sure you are killing the processes that are meant to be killed. Once verifed, simply run: db.currentOp(    {      "active" : true,      "secs_running" : { "$gt" : 10 },      "ns" : {$in:["<db1>.<col1>","<db2>.<col2>","<dbn>.<coln>
Read more