How To Upgrade From Goldengate Classic Extract To Integrated Extract Doc ID 1484313.1
Oracle GoldenGate - Version 22.214.171.124.0 and later Information in this document applies to any platform.
Steps to upgrade a Goldengate classic extract to integrated extract
To run integrated extract in 11.2.1 Goldengate , the following requirements should be met 1.Oracle RDBMS must be 126.96.36.199 or higher and 2.You must apply the RDBMS(Database) patches as suggested in the below MOS document
NOTE:1411356.1 - 188.8.131.52 Database specific bundle patch for Integrated Extract 11.2.x
The redo compatibility should be set to 184.108.40.206 matching the db version.
3. NOTE: STEP 3 IS SPECIFIC TO RAC ENVIRONMENTS AND OGG VERSIONS 220.127.116.11.23+. If using OGG version prior to 18.104.22.168.23 step 3 can be skipped.
To overcome below bug 18103455 OGG versions 22.214.171.124.23+ introduces a new TRANLOPTIONS option PREPAREFORUPGRADETOIE and a change to the procedure for switching from classic to integrated Extract.
Bug 18103455 – Replicat abends with “WARNING OGG-01154 SQL error 1403 mapping” because of missing data that extract skipped during a change from classic Extract to Integrated Extract.
A) For a running extract, issue the following command: SEND extract <extract name> tranlogoptions prepareforupgradetoie
B) For a stopped extract, start it after adding the following line to the parameter file:
C) Monitor the ggserr.log file or corresponding extract report file for an INFO GG-01873 message indicating the the change has taken affect and that you can proceed with the upgrade.
Example from report file: 2014-06-05 17:06:09 INFO OGG-01873 The parameter TRANLOGOPTIONS PREPAREFORUPGRADETOIE has taken effect. Proceed to the next step in the upgrade process.
Example from ggserr.log file: 2014-06-05 17:06:09 INFO OGG-01873 Oracle GoldenGate Capture for Oracle, src.prm: The parameter TRANLOGOPTIONS PREPAREFORUPGRADETOIE has taken effect. For the INFO message to show up extract has to process a committed transaction on all the RAC nodes for a table being captured. As an alternative a dummy table can be added
to the extract parameter file and doing DML on this table from all the threads would give extract commit boundary current checkpoints for all the threads
D) Once said message is detected, Stop the extract, perform dblogin, and alter for conversion to Integrated as shown below
4.Connect to the Extract database, and grant the following priviege to GG Admin user
SQL>exec dbms_goldengate_auth.grant_admin_privilege('<ggadmin>') Login into GGSCI
•Check to see if upgrade possible
GGSCI> DBLOGIN USERID <ID> PASSWORD <PW>
GGSCI> INFO <extract_name> UPGRADE
Upgrade may fail, in case of existing open transactions GGSCI>stop extract <extract_name> GGSCI>dblogin userid <ggadmin>,password <password> --Register the extract in the database if not done already GGSCI>register extract <extract_name> database