Upgrade Oracle Golden Gate 12cR1 to 12cR2

In this article, we will look at Oracle Golden Gate upgrade from 12.1 to 12.2 on a Linux server. Make sure you Allow golden gate processes to finish processing all current DML and DDL data in GG trail files.

• Golden Gate Upgrade Prerequisite

• Perform Golden Gate upgrade

Golden Gate Upgrade Prerequisite

Stop user activity on source objects which are involved in replication

Stop Extract

GGSCI> lag ext1
GGSCI> stop ext1

Make sure replicat applies all transactions on target

GGSCI> lag rep1

Stop pump and Replicat

GGSCI> stop dp1
GGSCI> stop rep1

Stop Manager on both source and target

GGSCI> stop mgr

Take backup of GG_HOME on both source and target

Perform Golden Gate upgrade

• Download the latest 12.2.0.2 Golden Gate and copy the zip file to both source and target DBs

• Unzip and start the runInstaller

• Give same old GG_HOME location while installation – Do not worry, this option will auto-upgrade old GG

• Do not start manager

• Perform installation on both source and target DBs in the same old GG_HOME location

Run @ulg script for supplemental log upgrade from GG_HOME

cd $GG_HOME
Sqlplus / as sysdba
SQL> @ulg.sql  press enter when prompted

Rollover Extract, Pump, and Replicat to next trail sequence number

On source DB:
=============
alter extract ext1 etrollover
alter extract dp1 etrollover
info ext1 detail
ALTER EXTRACT dp1, EXTSEQNO <above_seq_no>, EXTRBA 0
info dp1 detail

On target DB:
=============
alter replicat rep1, EXTSEQNO <above_seq_no>, EXTRBA 0

Start Manager, Extract, Pump, and Replicat

• This is an oracle known error. You get prvtlmpg.plb script with GG binaries. This resides under $GG_HOME.

• Run this script on both source and target database

cd $GG_HOME
Sqlplus / as sysdba
SQL> @prvtlmpg.plb

--> press enter when prompted

Allow activity on source objects involved in the replication.