Replicat Upgrade Considerations
All Replicat installations should be upgraded at the same time. It is critical to ensure that all trails leading to all Replicat groups on all target systems are processed until empty, according to the upgrade instructions.
Caution:
The hash calculation used by the @RANGE
function to partition data among Replicat processes has been changed. This change is transparent, and no re-partitioning of rows in the parameter files is required, so long as the upgrade is performed as directed in these instructions. To ensure data continuity, make certain to allow all Replicat processes on all systems to finish processing all of the data in their trails before stopping those processes, according to the upgrade instructions. Note that if the Replicat processes are not upgraded all at the same time, or the trails are not cleaned out prior to the upgrade, rows may shift partitions as a result of the new hash method, which may result in collision errors.
When upgrading from the 18c release of Oracle GoldenGate to the 19c (19.1.0) release, ensure that
you do not use the SOURCEDEF
parameter in Replicat, otherwise the Replicat
will abend. However, if the trail file format is pre-12.2, then SOURCEDEF
is still required because no metadata exists in the trail file.
For
PostgreSQL: When upgrading from 12.2.0.1 to
19c (19.1.0), you need to run the UPGRADE
HEARTBEATTABLE
command from GGSCI to
upgrade the heartbeattable to include the
LOGBSN
columns
Parent topic: Scope of the Upgrade Procedure