What you will learn
Separate installation, patching, and process migration into distinct gates. A new software home can be prepared before any production process is stopped.
Before you begin
Use an isolated Oracle Database/GoldenGate combination certified for your exact platform and release. The examples use GoldenGate 19c Classic Architecture and GGSCI; Microservices deployments use different administrative workflows. Configure credential-store aliases, required database privileges, keys, supplemental logging, and a verified backup. Example groups are EDEMO (Extract), PDEMO (pump), and RDEMO (Replicat); first confirm the actual names in your lab. Confirm supported database/client libraries, OS architecture, free space, filesystem ownership, and the exact patch readme. Use dedicated software and trail directories with a recorded backup.
1. Inventory the existing boundary
INFO ALL
INFO EXTRACT EDEMO, DETAIL
INFO REPLICAT RDEMO, DETAIL
Save process type, trail prefix, sequence/RBA, lag, checkpoint age, and database/service identity. A process can be RUNNING while no useful transaction is reaching the target.
2. Prepare the destination software
Install verified media into a separate home using the vendor-supported installer. Apply only the matching patch procedure and retain installer/patch logs. Check the executable version and library resolution before starting a process. For RAC, validate the intended database service through a client connection and confirm its failover behavior.
3. Prepare credentials and configuration
CREATE SUBDIRS
INFO ALL
For a new Classic home, CREATE SUBDIRS prepares its working subdirectories. Configure Manager with the approved port policy and credential-store aliases through the documented secure workflow. Transfer credential material only using a supported protected procedure; never place plaintext passwords into copied examples.
4. Preserve a known restart position
Quiesce affected writes where the plan requires it, allow the pipeline to reach the agreed boundary, stop groups cleanly, and record sequence/RBA plus checkpoint details. Preserve every trail segment still needed by downstream readers and use the vendor-supported process/checkpoint migration method. Do not delete groups before preserving their state.
5. Start in dependency order and prove continuity
Verify the new Manager/transport endpoint, then start the prepared capture/transport/apply path according to the migration plan. Confirm checkpoint progression and inspect reports. Commit a synthetic source transaction and verify its target result before switching ownership of monitoring and scheduled operations.
Example output
The following is an illustrative, normalized lab result, not output captured from a live customer system. Your versions, addresses, timings, and row counts will differ.
Illustrative INFO ALL snapshot:
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING EDEMO 00:00:00 00:00:02
EXTRACT RUNNING PDEMO 00:00:00 00:00:01
REPLICAT RUNNING RDEMO 00:00:00 00:00:01
This normalized snapshot shows the example groups only; real group placement differs by host. A pump is reported as EXTRACT. RUNNING and zero checkpoint lag are not proof of data correctness—commit a synthetic transaction and verify its target result as described above.
Verify the result
The intended binaries and database services are in use, trail/checkpoint positions progress without a gap, and inserts, updates, and deletes reach the target. For RAC, rehearse a supported service failover and verify capture/apply remain correct after reconnection.
Troubleshooting
A missing-trail error requires identifying the exact requested sequence and whether a valid retained copy exists. Advancing the checkpoint to the newest trail can skip transactions. Library or connection errors require checking Oracle homes, service names, wallet/alias configuration, and certification.
Recovery and next steps
Retain the old software and state until acceptance. If the new path fails before new writes/apply diverge, use the documented restart plan at the saved boundary. After divergence, reconcile state before changing direction. Never start two independent copies of the same apply path against one target.