{"id":5276,"date":"2024-08-02T07:00:00","date_gmt":"2024-08-02T04:00:00","guid":{"rendered":"https:\/\/www.dataplatform.gr\/?p=5276"},"modified":"2024-08-02T01:19:24","modified_gmt":"2024-08-01T22:19:24","slug":"pos-rythmizoyme-to-replication-toy-goldengate-oste-na-diav","status":"publish","type":"post","link":"https:\/\/www.dataplatform.gr\/en\/pos-rythmizoyme-to-replication-toy-goldengate-oste-na-diav-2\/","title":{"rendered":"How do we configure GoldenGate replication to read from Oracle Data Guard Standby"},"content":{"rendered":"

In this article we will see how we can set one up extract process <\/em><\/strong>so that it can export its trail files from the Standby logs without affecting the Primary. This way is called Classic Capture in Active Data Guard (ADG) only mode<\/strong>. <\/p>\n\n\n\n

As the name suggests, the extract process it cannot work in integrated but only in the old classic capture<\/strong> (we can read the differences between integrated and classic capture here<\/a>).<\/p>\n\n\n\n

The limitations don't end here as we can't replicate compressed tables and we can't enable supplemental logging on only a specific table (add trandata<\/code>) and we need to enable it in the whole schema (add schematrandata<\/code>). <\/p>\n\n\n\n

We can read the limitations of ADG mode here<\/a>.<\/p>\n\n\n\n

The prerequisites<\/h2>\n\n\n\n

For this article we assume that we already have a complete GoldenGate installation.<\/p>\n\n\n\n

How to install and configure can be read in the article here<\/a>.<\/p>\n\n\n\n

Then we must have installed the GoldenGate software on Standby or have it on a shared disk.<\/p>\n\n\n\n

The footsteps<\/h2>\n\n\n\n

In this particular installation we have chosen to have GoldenGate installed on a shared disk, so we will have to raise the GoldenGate manager from StandBy.<\/p>\n\n\n\n

Go to the folder where the installation is located (we have passed the path to the environment) and connect to the GoldenGate interface:<\/p>\n\n\n\n

cd $GGHOME\n\nggsci<\/code><\/pre>\n\n\n\n
We start the manager:<\/p>\n\n\n\n
start manager<\/pre>\n\n\n\n
After starting the manager, we should connect through ggsci of Standby to Primary in order to activate supplemental logging (we don't have the option from Standby):<\/p>\n\n\n\n
dblogin useridalias ggadmin<\/pre>\n\n\n\n
add schematrandata stratos<\/pre>\n\n\n\n
Then we create the credentialstore that will connect to the Standby (where oracledb_dr is the tnsnames entry for the Standby):<\/p>\n\n\n\n
add credentialstore\nalter credentialstore add user ggadmin@oracledb_dr alias ggadmin_dr<\/pre>\n\n\n\n
Then we connect with the alias we made in Standby:<\/p>\n\n\n\n
dblogin useridalias ggadmin_dr<\/pre>\n\n\n\n
Then we edit the extract and add it TRANLOGOPTION MINEFROMACTIVEDG<\/code>:<\/p>\n\n\n\n
edit param ora_ext<\/pre>\n\n\n\n
EXTRACT ora_ext
USERIDALIAS ggadmin_dr
TRANLOGOPTION MINEFROMACTIVEDG
RMTHOST sqlserverhost.mshome.net, MGRPORT 7809
RMTTRAIL .\/dirdat\/aa
TABLE STRATOS.*;<\/code><\/pre>\n\n\n\n
Then we are careful by registering the extract not to put the integrated parameter <\/strong>as we said it should be classic capture:<\/p>\n\n\n\n
add extract ora_ext, tranlog, begin now\nadd rmttrail .\/dirdat\/aa , ext ora_ext<\/pre>\n\n\n\n
That was it, now replication will be done from Standby, all we have to do is start the extract process:<\/p>\n\n\n\n
start ora_ext<\/pre>\n\n\n\n
<\/p>\n\n\n\n
Sources:<\/h2>\n\n\n\n