Patching Oracle GoldenGate Classic Architecture for Non-Oracle Databases

The following steps guide you to install patches for any of the non-Oracle databases released for Oracle GoldenGate.

(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 and target systems, as applicable) Expand the patch version 19c (19.1.0) of Oracle GoldenGate into a new directory on each system (not the current Oracle GoldenGate directory). Do not create the sub-directories, just complete the steps to the point where the installation files are expanded.
(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 the LOGEND 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 the STATUS 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 return At 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
```
(Source and target systems) Move the expanded Oracle GoldenGate files from the new directory to your existing Oracle GoldenGate directory on the source and target systems.
(DB2 for i) Run ggos400install without arguments. No arguments are necessary for an upgrade, however, if you change the library, the old library is left on the system until you remove it. For more information about ggos400install, see Prerequisites for Installing Oracle GoldenGate for DB2 for i.
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.
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
```

Also see:

For MySQL 5.7, see instructions for patching in Patching Oracle GoldenGate MySQL 5.7 with DDL Replication Enabled
For SQL Server, see Patching Oracle GoldenGate for SQL Server - Extract Requirements