Skip to Main Content

GoldenGate

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

How to minimize downtime when target/replicate side host is changed

DDebJul 31 2020 — edited Aug 13 2020

Hello experts,

                       We are planning to change target/replicate side host platform of Goldengate and target DB (Solaris to Linux) and also we will upgrade GG from 12.1.2.1.0 to 19.1.0.0.4.Right now in source side we have 19c db and GG setup with version 19.1.0.0.

and target side 12.1.0.2 db with 12.1.2.1.0.

Since there is no change in source side so we have to consider minimal downtime for source side.I have thought like below.Please comment and suggest if you think differently.

Since there is no change in extract path I will not touch any parameter file in extract process but will change parameter file fro pump process.

  

  1. Install 19c Goldengate binary in in new Linux platform with only manager process running
  2. Delete existing pump process in source solaris host
  3. Update pump process parameter file with correct remote host,mgr port and trail file path in source
  4. Add extract pump process with correct extttrailsource in source
  5. Add remote trail with correct path
  6. Now all changes from source db will be extracted and pumped to remote trail file in remote Linux host where 19c Goldengate is running.
  7. Complete db migration to Linux host
  8. Now configure replicate process in Linux host like below

       ADD replicat group_name  BEGIN , EXTSEQNO sequence_number/timestamp

Please comment/suggest on these steps.

Regards

Dhritiman Deb

Comments
Post Details
Added on Jul 31 2020
5 comments
188 views