Installing patches is different from Upgrading to Oracle GoldenGate 12c (12.3.0.1). This chapter describes the steps to prepare and install patches.
Topics:
Download the appropriate patches for the Oracle GoldenGate build for each system that will be part of the Oracle GoldenGate configuration.
Note:
Before installing the software, see Release Notes for Oracle GoldenGatefor any new features, parameter changes, upgrade requirements, known issues, or bug fixes that affect your current configuration.
Parent topic: Installing Patches for Oracle GoldenGate
This section provides the prerequisites and steps for installing the Oracle GoldenGate patches for Oracle.
Topics:
Once the patch is downloaded, you need to prepare your environment before you can install it (you need to meet these prerequisites prior to deinstalling, too). To do so, ensure that your system meets the following requirements:
Parent topic: Patching Oracle GoldenGate for Oracle
To install the patch, use this procedure:
Maintain a location for storing the contents of the patch ZIP file. In the rest of the document, this location (absolute path) is referred to as PATCH_TOP_DIR
.
Extract the contents of the patch ZIP file to the location you created in the previous step.
For example:
$ PATCH_TOP_DIR p14309369_112101_Solaris86-64.zip
Stop Oracle GoldenGate by doing the following:
Run GGSCI.
Stop Manager by running the command:
STOP MANAGER
Stop all Oracle GoldenGate processes by running the command:
STOP ER *
Navigate to the PATCH_TOP_DIR
/Patch_number
directory:
$ cd PATCH_TOP_DIR/Patch_number
Install the patch by running the following command:
$ opatch apply
Note:
When OPatch starts, it validates the patch and ensures that there are no conflicts with the software already installed in the ORACLE_HOME
of the Oracle GoldenGate release. OPatch categorizes conflicts into the following types:
Conflicts with a patch already applied to the ORACLE_HOME
. In this case, stop the patch installation and contact Oracle Support Services.
Conflicts with a patch already applied to the ORACLE_HOME
that is a subset of the patch you are trying to apply. In this case, continue with the patch installation because the new patch contains all the fixes from the existing patch in the ORACLE_HOME
. The subset patch will automatically be rolled back prior to the installation of the new patch.
If the patch includes new parameters, edit the respective parameter files.
Set ORACLE_HOME
back to the Oracle database home directory.
Start the processes from the Oracle GoldenGate home by doing the following:
Invoke GGSCI.
Start Manager by running this command:
START MANAGER
Start all Oracle GoldenGate processes by running this command:
START ER *
Exit GGSCI.
Parent topic: Patching Oracle GoldenGate for Oracle
The following steps guide you to install patches for any of the heterogeneous 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 12c (12.3.0.1.x) 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
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
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 Installing DB2 for i in Installing Oracle GoldenGate .
Note:
(Only for the Oracle GoldenGate for SQL Server CDC Extract) Before performing this step, review the steps for Patching Oracle GoldenGate for SQL Server - CDC Extract Requirements.GGSCI> START MANAGER GGSCI> START EXTRACT group GGSCI> START EXTRACT pump GGSCI> START REPLICAT group
metadata_server
by executing the following:
./ddl_install.sh start user-id password port-number
To patch the Oracle GoldenGate for SQL Server CDC Extract, see:
Parent topic: Installing Patches for Oracle GoldenGate
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 for Heterogeneous Databases 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 a FILTERTABLE
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.
Parent topic: Patching Oracle GoldenGate for Heterogeneous Databases