Consider currently Non-integrated parallel replicat is running and observed slow apply and decided to convert the replciat into Integrated replicat – In this blog post we will cover this method.
Non-Integrated Parallel vs Integrated Replicat
Classic Parallel Replicat achieves parallelism by running multiple GoldenGate processes, whereas Integrated Replicat achieves parallelism by leveraging the Oracle database’s internal apply engine, ensuring transactional consistency, referential integrity, and higher scalability.
Reference: https://docs.oracle.com/en/middleware/goldengate/core/23/coredoc/replicat-integrated-replicat.html?utm_source=chatgpt.com#GUID-07989210-6995-45FA-A707-C8F1DE38CA9B
Connect to the existing Non-integrated Replicat
In the checkpoint tab we have to fetch the both sequence number and the Transacation log RBA offset value. This value used in new replciat, so that we are guiding new replicat to start reading data from this point.
Create new integrated replicat
Enter the replicat credentials and trail location and also trail name.
We need to provide the sequence and the RBA offset of when the non-integarted replicat was stopped.
Complete the replicat with the parameters
Now start the new replicat, it should fetch the from the same point from where classic replicat has stopped.
Converting a non-integrated (classic) Replicat to an integrated Replicat from the same checkpoint is a strategic modernization step rather than a simple configuration change. By reusing the existing trail files and preserving the replication position, this approach enables a seamless transition without re-initial load or data resynchronization, while shifting the apply logic from an external GoldenGate process into the Oracle database itself.
