Switch to Integrated Replicat

Earlier I wrote a blog post about moving the Oracle Golden Gate Extract from “Classic”  capture to “Integrated” capture.   In this post, we will take a look at how to move a “Classic” replicat (apply) to an “Integrated” replicat (apply) process.
The initial step to migrate the replicat from “Classic” to “Integrated” are the same as the extract.  Look here for the initial details.  This post picks up when we are getting ready to stop the replicat and perform the migration.
Before we can do anything with the replcat, we need to be in GGSCI.
Code 1:
[code language=”css”]
[oracle@oel oggcore_1]$ ./ggsci
Oracle GoldenGate Command Interpreter for Oracle
Version 12.1.2.0.0 17185003 17451407_FBO
Linux, x64, 64bit (optimized), Oracle 11g on Oct 29 2013 00:31:40
Operating system character set identified as UTF-8.
Copyright (C) 1995, 2013, Oracle and/or its affiliates. All rights reserved.
 
GGSCI (oel.acme.com) 1>
[/code]
Now, we need to stop the replciat (apply) process that we are using.
Code 2:
[code language=”css”]
GGSCI (oel.acme.com) 1> info all
Program     Status      Group       Lag at Chkpt  Time Since Chkpt
MANAGER     RUNNING
JAGENT      STOPPED
EXTRACT     RUNNING     EXT         00:00:09      00:00:00
EXTRACT     RUNNING     PMP         00:00:00      00:00:10
REPLICAT    RUNNING     REP         00:00:00      00:00:08
GGSCI (oel.acme.com) 2> stop replicat rep
Sending STOP request to REPLICAT REP …
Request processed.
[/code]
With the replicat stopped, we need to log into the database through GGSCI.
Code 3:
[code language=”css”]
GGSCI (oel.acme.com) 3> dblogin userid ggate, password ggate
Successfully logged into database.
[/code]
Next, we need to alter the replicat to make it integrated.
Code 4:
[code language=”css”]
GGSCI (oel.acme.com) 4> alter replicat rep, integrated
REPLICAT (Integrated) altered.
[/code]
Finally, we need to start the replicat.
Code 5:
[code language=”css”]
GGSCI (oel.acme.com) 5> start replicat rep
Sending START request to MANAGER …
REPLICAT REP starting
[/code]
Once the replicat has been started, we can check the replicat and look at the details with the INFO option.
Code 6:
[code language=”css”]
GGSCI (oel.acme.com) 7> info replicat rep, detail
REPLICAT   REP       Last Started 2014-04-21 14:06   Status RUNNING
INTEGRATED
Checkpoint Lag       00:00:00 (updated 00:00:03 ago)
Process ID           28410
Log Read Checkpoint  File ./dirdat/rt000000
                     2014-04-21 12:42:14.030503  RBA 6912167
INTEGRATED Replicat
DBLOGIN Provided, inbound server name is OGG$REP in ATTACHED state
Current Log BSN value: <NULL>
  Extract Source                          Begin             End
  ./dirdat/rt000000                       2014-04-21 12:42  2014-04-21 12:42
  ./dirdat/rt000000                       2014-04-21 12:42  2014-04-21 12:42
  ./dirdat/rt000000                       * Initialized *   2014-04-21 12:42
  ./dirdat/rt000000                       * Initialized *   2014-04-21 12:42
  ./dirdat/rt000000                       * Initialized *   First Record
  ./dirdat/rt000000                       * Initialized *   First Record
Current directory    /oracle/app/product/12.1.2/oggcore_1
Report file          /oracle/app/product/12.1.2/oggcore_1/dirrpt/REP.rpt
Parameter file       /oracle/app/product/12.1.2/oggcore_1/dirprm/REP.prm
Checkpoint file      /oracle/app/product/12.1.2/oggcore_1/dirchk/REP.cpr
Checkpoint table     ggate.checkpoint
Process file         /oracle/app/product/12.1.2/oggcore_1/dirpcs/REP.pcr
Error log            /oracle/app/product/12.1.2/oggcore_1/ggserr.log
[/code]
From looking at the details of the replicat, you can see that it is now integrated and using the DBLOGIN that we provided earlier.
Enjoy!
twitter: @dbasolved
blog: http://dbasolved.com

Please follow and like: