Splitting an existing replicat ( or extract ) with the RANGE command into multiple replicats (extracts)
(Doc ID 1320133.1)
Last updated on MARCH 12, 2021
Oracle GoldenGate - Version 5.0.0 and later Information in this document applies to any platform.
***Checked for relevance on 05-Nov-2012***
Often, a single existing replicat has insufficient performance for the load it is processing. The insufficiency may be constant or may be occasional due to increases in loads. Batch jobs frequently are the cause of the increased load.
It is possible to take an existing replicat and split it into multiple replicats thus splitting the load and increasing the effective throughput.
This article shows how to split a replicat into 3 replicats. It would also work, with variations, for extracts. The actual number of replicats could be from two to many.
Please note the implications for transactional integrity discussed at the end of the technique.
This applies to all platforms and installs.
There are caveats for transactional integrity, locking and timing of processing.
Using RANGE breaks up transactional integrity.
Using multiple replicats can mean one replicat gets ahead of others. This is especially of concern if DDL is being replicated as RANGE does not support DDLs
Using multiple replicats may introduce locking issues.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!