4 Installing Patches for Oracle GoldenGate

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:

4.1 Downloading Patches for Oracle GoldenGate

Download the appropriate patches for the Oracle GoldenGate build for each system that will be part of the Oracle GoldenGate configuration.

  1. Using a browser, navigate to http://support.oracle.com.
  2. Log in with your Oracle ID and password.
  3. Select the Patches and Upgrades tab.
  4. On the Search tab, click Product or Family.
  5. In the Product field, type Oracle GoldenGate.
  6. From the Release drop-down list, select the release version that you want to download.
  7. Make certain that Platform is displayed as the default in the next field, and then select the platform from the drop-down list.
  8. Leave the last field blank.
  9. Click Search.
  10. In the Patch Advanced Search Results list, select the patch that best meets your search criteria, making certain that the Oracle GoldenGate patch that you select corresponds to the version of the database that will be used.

    When you select the build, a dialog box pops up under the build description, and then you are advanced to the download page.

  11. Click the Patch file name link for each patch that you want to download. The File Download dialog box appears.
  12. Select either Open with or Save File:
    To... Select...

    Extract the patch immediately

    Open with, then select the desired file extraction utility and extract the files to a location on your file system.

    Save the patch for later extraction

    Select Save file, then save to a directory on your file system.

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

4.2 Patching Oracle GoldenGate for Oracle

This section provides the prerequisites and steps for installing the Oracle GoldenGate patches for Oracle.

Topics:

Parent topic: Installing Patches for Oracle GoldenGate

4.2.1 Preparing to Patch

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:

  1. Ensure that the Oracle GoldenGate version on which you are installing the patch or from which you are rolling back the patch is Oracle GoldenGate release 12c (12.3.0.1) for Oracle.
  2. Use the latest version of OPatch. If you do not have the latest version, follow the instructions outlined in the My Oracle Support note 224346.1, available at:
  3. Set the ORACLE_HOME environment variable to the Oracle GoldenGate installation directory, which is referred to as ORACLE_HOME.
  4. Set the PATH environment variable to include the location of the unzip executable, and the ORACLE_HOME and the ORACLE_HOME/OPatch directories present in the Oracle GoldenGate home.
  5. Verify the Oracle Inventory, which OPatch accesses to install the patches. To verify the inventory, run the following command: 
    $ opatch lsinventory

    If the command displays any errors, contact Oracle Support and resolve the issue.

Parent topic: Patching Oracle GoldenGate for Oracle

4.2.2 Installing Patches

To install the patch, use this procedure:

  1. 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.

  2. 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

  3. Stop Oracle GoldenGate by doing the following:

    1. Run GGSCI.

    2. Stop Manager by running the command:

      STOP MANAGER

    3. Stop all Oracle GoldenGate processes by running the command:

      STOP ER *

  4. Navigate to the PATCH_TOP_DIR/Patch_number directory:

         $ cd PATCH_TOP_DIR/Patch_number

  5. 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.

  6. If the patch includes new parameters, edit the respective parameter files.

  7. Set ORACLE_HOME back to the Oracle database home directory.

  8. Start the processes from the Oracle GoldenGate home by doing the following:

    1. Invoke GGSCI.

    2. Start Manager by running this command:

      START MANAGER

    3. Start all Oracle GoldenGate processes by running this command:

      START ER *

    4. Exit GGSCI.

Parent topic: Patching Oracle GoldenGate for Oracle

4.3 Patching Oracle GoldenGate for Heterogeneous Databases

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

  1. (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).

  2. (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.

  3. (Source system) Stop user activity on objects in the Oracle GoldenGate configuration.

  4. (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
  5. (Source system) In GGSCI, stop Extract and data pumps: 
     GGSCI> STOP EXTRACT group

  6. (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

  7. (Target systems) In GGSCI, stop all Replicat processes:

    GGSCI> STOP REPLICAT group
  8. (Source and target systems) In GGSCI, stop Manager on the source and target systems. 
    GGSCI> STOP MANAGER

  9. (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

  10. (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.

  11. (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 .

  12. 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.
    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
  13. (Source for MySQL with DDL replication enabled) Restart the 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

4.3.1 Patching Oracle GoldenGate for SQL Server - CDC Extract Requirements

You must follow the existing patching procedures in Patching Oracle GoldenGate for Heterogeneous Databases. In addition, you must re-run ADD TRANDATA for each table that is already enabled for TRANDATA using these steps:

  1. Stop all Oracle GoldenGate processes

  2. Follow normal patch procedures for binary replacement but do not start any Oracle GoldenGate processes. See Patching Oracle GoldenGate for Heterogeneous Databases for details.

  3. 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.

  4. Ensure that the Extract is stopped.

  5. 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.

  6. Manually restart the SQL Server CDC Capture job.

  7. Manually restart the Oracle GoldenGate processes such as Extract, Replicat, and Manager.

Parent topic: Patching Oracle GoldenGate for Heterogeneous Databases