OGG Upgrade steps on system hosting
Goldengate during DB upgrade (OL)
The DB upgrade is happening on source OL flpd11504.ffdc.sbc.com. DB currently
is on 12c. Its getting upgraded to 19c. OGG version 19.1.0.0.4 is being used.
We also will be upgrading OGG to 19c on OL flpd11504.ffdc.sbc.com server. We
need to install OGG version 19c for 19c database. Hence we need to follow below
steps:
|
Source
1: OL 12c DB and
OGG 19.1.0.0.4 – Here DB and GG will be upgraded to 19c flpd11504.ffdc.sbc.com.ffdc.sbc.com sudo -iu
p1bbn2d9g DB is in 12c
now and is upgrading to 19c To
connect to DB: Login to : voyagerdb.snt.bst.bls.com sudo -iu
oracle sqlplus ggs/take14team@p1bbn2d9.DB.ATT.COM |
Steps on Source flpd11504.ffdc.sbc.com(OGG 11g home):
Once application shutdown is completed:
|
cd /opt/app/p1bbn2d9/ggs/19.1.0.0.4 ./ggsci Stop Extract , pump processes:
|
Below steps needs to be done on target flph1167 once
application Is stopped (It is continuation of above):
Steps on Target (flph1167.ffdc.sbc.com):
|
cd /opt/app/p2bbn2d4/ggs/12.3.0.1.4 30 Replicats |
Wait until there is no lag on replicats, stop
replicat processes.
|
Send Replicat
*,logend (Once the
output received is Yes) STOP Replicat
R* |
Move all trail files on flph1167 server under backup folder
|
cd /opt/app/p2bbn2d4/ggs/12.3.0.1.4/trails mkdir backup_new mv vt*
backup_new mv rt*
backup_new Ensure that
there is no lt and rt present in this location |
4. on source flpd11504.ffdc.sbc.com, Take the backup of
existing Goldengate home:
mv /opt/app/p1bbn2d9/ggs/19.1.0.0.4 /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c
5. Ask
SDBAs to uninstall Goldengate from existing environment and Install OGG 19.1.0.0.4 (ogg_191004 present
in /orasoft/stage/linux_x86_64bit) under /opt/app/p1bbn2d9/ggs/19.1.0.0.4
cd /opt/app/p1bbn2d9/ggs/19.1.0.0.4/deinstall
./deinstall.sh
Once deinstallation is completed remove Goldengate home:
Rm -rf /opt/app/p1bbn2d9/ggs/19.1.0.0.4
Once deinstall is completed proceed with Installation of
Goldengate in below location:
/opt/app/p1bbn2d9/ggs/19.1.0.0.4
(Choose appropriate DB version during
installation) .
Get 770
permission on 19.1.0.0.4
chmod
770 19.1.0.0.4
6. Upgrade database.
After upgrade of database,
(from the new GG HOME)(19c OGG home):
|
Ask SDBA to
run below: cd /opt/app/p1bbn2d9/ggs/19.1.0.0.4 A. Connect
to DB as sysdba: SQL>@ulg.sql This script converts the
existing supplemental log groups to the new format required by the new
release. This step is required even if
you plan to use the new triggerless capture method. The script should run without
error; if errors occur, contact Oracle Support. B.
Verify DB parameter(SDBA tasks) Alter system
set enable_goldengate_replication=TRUE; execute dbms_goldengate_auth.grant_Admin_privilege(‘GGS’); select
CAPTURE_NAME, STATUS from dba_capture; alter
database add supplemental log data(all) columns; alter
database force logging; |
Once SDBA gives us go ahead proceed with below:
cd /opt/app/p1bbn2d9/ggs/19.1.0.0.4
7. Copy
goldengate process related files from old goldengate home (/opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c)
to the new 19.1.0.0.4 goldengate home (/opt/app/p1bbn2d9/ggs/19.1.0.0.4) like
.prm in appropriate directories. Also copy dirdef folder from old to new 19c OGG home.
Below
needs to be done in 19.1.0.0.4 OGG HOME and after DB upgrade is done:
|
mkdir -p /opt/app/p1bbn2d9/ggs/19.1.0.0.4/admin mkdir -p /opt/app/p1bbn2d9/ggs/19.1.0.0.4/trails cp -R /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/admin/*
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/admin/ cp -R /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/dirdef/*
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/dirdef cp -R /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/dirprm/*
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/dirprm cp /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/GLOBALS
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/GLOBALS --cp -R /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/dirchk/*
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/dirchk --cp -R /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/trails/*
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/trails --mv /opt/app/p1bbn2d9/ggs/19.1.0.0.4/BR
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/BR_bkp --cp -R /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/BR
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/BR cp -R /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/dirwlt/*
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/dirwlt cp -R /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/dircrd/*
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/dircrd cp /opt/app/p1bbn2d9/ggs/19.1.0.0.4_12c/ENCKEYS
/opt/app/p1bbn2d9/ggs/19.1.0.0.4/ENCKEYS Note: Highlighted in red not
required to be copied |
|
GGSCI> Dblogin
useridalias ggs Add extract EP2BBN2D,integrated tranlog,begin now Add extract EVENUS,integrated tranlog,begin now Register extract ep2bbn2d,database Register extract evenus,database Add exttrail /opt/app/p1bbn2d9/ggs/19.1.0.0.4/dirdat/lt,extract
EP2BBN2D Add exttrail /opt/app/p1bbn2d9/ggs/19.1.0.0.4/dirdat/vt,extract
EVENUS Add extract PP2BBN2D,exttrailsource /opt/app/p1bbn2d9/ggs/19.1.0.0.4/dirdat/lt Add extract PVENUS,exttrailsource /opt/app/p1bbn2d9/ggs/19.1.0.0.4/dirdat/vt Add rmttrail /opt/app/p2bbn2d4/ggs/12.3.0.1.4/trails/rt,extract
PP2BBN2D Add rmttrail /opt/app/p2bbn2d4/ggs/12.3.0.1.4/trails/vt,extract
pvenus |
8. Start extract and pump
|
Start EP2BBN2D Start EVENUS Start PP2BBN2D Start PVENUS |
Below needs to be done in Target flpd1167 server:
9. Start all the replicats..also verify the connection to
the new upgraded database.
|
--Note
down the new trail file number generating in trail location from p* from
source and alter the replicats to that sequence. Alter
R*,extseqno 0,extrba 0 START R* |
Release the database to app team,
Goldengate related ADBA tasks are completed by this step
10. After ensuring all goldengate processes are running,
start the applications accessing the database.
.
No comments:
Post a Comment