srt9i2019 Document 1484913. Copyright (¢) 2018, Orde Al rights reserved, Orale Conldental How To Upgrade From Goldengate Classic Extract To Integrated Extract (Doc ID 1484313.1) In this Document Goal Solution References Oracle GoldenGate - Version 11.2.1.0.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 L.Oracle ROBMS must be 11.2,0.3 or higher and 2.You must apply the RDBMS(Database) patches as suggested in the below MOS document NOTE:1411356.1 - 11.2.0.3 Database specific bundle patch for Integrated Extract 11.2.x The redo compatibility should be set to 11.2.0.3 matching the db version, 3. NOTE: STEP 3 IS SPECIFIC TO RAC ENVIRONMENTS AND OGG VERSIONS 11.2.1.0.23+, If using OGG version prior to 11.2.1.0.23 step 3 can be skipped. To overcome below bug 18103455 OGG versions 11.2.1.0.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 dassic Extract to Integrated Extract. A) For a running extract, issue the following command: SEND extract tranlogoptions prepareforupgradetole B) For a stopped extract, start it after adding the following line to the parameter file: ‘TRANLOGOPTIONS PREPAREFORUPGRADETOIE ©) 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 QGG-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. hitps:/support oracle.comfepmositaces/DocumentDisplay?_adtcti-state=1Ouhapinj4_178id=148413.1 wesrt9i2019 Document 1484913. 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 sald 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 soLvexee dbms_goldengate_auth.grant_admin_privilege ("") Login inte Gesct scheck to see if GGSCI> DBLOGIN rade possib! RID PASS! R GGSCI> INFO Ul of existing open transactions rade may fail, 41 a userid , password , upgrade integrated tranlog NOTE:1411356.1 - 1.2.0.3 Database Specific Bundle Patches for Integrated Extract 11.2.x Didnt find what you are looking for? hitps/Isupportoracle.comlepmosifaces/DacumentDisplay?_ad!ctt-state=10uh2pinj4_1718