5 Patching Oracle GoldenGate Classic Architecture for Non-Oracle Databases
For non-Oracle databases, Oracle GoldenGate Classic Architecture patches are complete installations and can be applied as a new installation or over an existing installation.
-
(Source and target systems) Back up the current Oracle GoldenGate installation directory on the source and target systems, and any working directories that you have installed on a shared drive in a cluster (if applicable).
-
(Source system) Stop user activity on objects in the Oracle GoldenGate configuration.
-
(Source system) In GGSCI on the source system, issue the
SEND EXTRACT
command with theLOGEND
option until it shows there is no more data in transaction log to process.GGSCI> SEND EXTRACT group LOGEND
-
(Source system) In GGSCI, stop Extract and data pumps:
GGSCI> STOP EXTRACT group
-
(Target systems) In GGSCI on each target system, issue the
SEND REPLICAT
command with theSTATUS
option until it shows a status of "At EOF" to indicate that it finished processing all of the data in the trail. This must be done on all target systems until all Replicat processes returnAt EOF
.GGSCI> SEND REPLICAT group STATUS
-
(Target systems) In GGSCI, stop all Replicat processes:
GGSCI> STOP REPLICAT group
-
(Source and target systems) In GGSCI, stop Manager on the source and target systems.
GGSCI> STOP MANAGER
-
(Source for MySQL with DDL replication enabled) Ensure that there are no new DDL operations during the patching process, then stop the metadata server by executing the following:
./ddl_install.sh stop user-id password port-number
For MySQL 5.7, see instructions for patching in Patching Oracle GoldenGate MySQL 5.7 with DDL Replication Enabled.
-
Copy the Oracle GoldenGate latest version ZIP file to the existing Oracle GoldenGate location. You can do so by removing or replacing the existing ZIP file.
-
Unzip and then untar the zip file. This will install Oracle GoldenGate patched version to the Oracle GoldenGate location, however all the subdirectories starting with
dir
(dirdat
for trail file,dirchk
for checkpoint table and so on) will not be overwritten.The command to perform this task would be similar to the following:
tar -xvf ggs_Linux_x64_MySQL_64bit.zip
For Windows, unzip the patch file.
-
Note:
(Only for the Oracle GoldenGate for SQL Server Extract) Before performing this step, review the steps for Patching Oracle GoldenGate for SQL Server - Extract Requirements.Note:
(Only for Oracle GoldenGate for PostgreSQL) For Oracle GoldenGate for PostgreSQL installations patched to release versions 21.8.0.0.2 and later, prior to restarting the Extracts and Replicats, update the DSN entries in theodbc.ini
file to take advantage of the new driver version. For more information, see Patching Oracle GoldenGate for PostgreSQL to Release Version 21.8.0.0.2 and Later.In GGSCI, start the Oracle GoldenGate processes on the source and target systems in the following order:GGSCI> START MANAGER GGSCI> START EXTRACT group GGSCI> START EXTRACT pump GGSCI> START REPLICAT group
-
(Source for MySQL with DDL replication enabled) Restart the
metadata_server
by executing the following:./ddl_install.sh start user-id password port-number
-
Verify that the Extract and Replicat processes are running.
Patching Oracle GoldenGate for SQL Server - Extract Requirements
ADD
TRANDATA
for each table that is already enabled for
TRANDATA
using these steps:
-
Stop all Oracle GoldenGate processes.
-
Follow normal patch procedures for binary replacement but do not start any Oracle GoldenGate processes. See Patching Oracle GoldenGate Classic Architechture Using OPatch for details.
-
Manually stop the SQL Server CDC Capture job for the database. If the job is processing a large transaction, it may take some time before it actually stops.
-
Ensure that the Extract is stopped.
-
Using GGSCI, run
ADD TRANDATA
again for every table that you previously enabled it for, including the heartbeat tables and any Replicat checkpoint table used as aFILTERTABLE
object for active/active configurations.Note:
Do not run the
DELETE TRANDATA
command. -
Manually restart the SQL Server CDC Capture job.
-
Manually restart the Oracle GoldenGate processes such as Extract, Replicat, and Manager.
Patching Oracle GoldenGate MySQL 5.7 with DDL Replication Enabled
To patch Oracle GoldenGate MySQL 5.7 with DDL replication enabled:
-
Stop the metadata server using the following DDL install script
stop
option../ddl_install.sh stop user-id password port-number
-
Replace the
metadata_server
executable in the installation directory. -
Start the metadata server running currently using ddl install script start option:
./ddl_install.sh start user-id password port-number
Note:
The DDL operations issued in between starting and stopping themetadata_server
would be lost.