Patching Oracle GoldenGate for SQL Server

Follow the existing patching procedures discussed in previous topics, Downloading Patches for Oracle GoldenGate and Patching Oracle GoldenGate Microservices Architecture Using OPatch. In addition, depending on your configuration of Oracle GoldenGate for SQL Server, you may be required to perform either of these steps.

Re-Run ADD TRANDATA

If patching a deployment where an Extract exists, it is recommended to re-run Add TRANDATA for each table that is already enabled for TRANDATA in order to update any Oracle GoldenGate dependent procedures or objects that may have changed for a given patch release. If changes to Oracle GoldenGate objects are part of a patch but have not been updated against the GoldenGate objects in the database, the Extract will fail to start and return an error about incorrect object versioning.

  1. Stop Extract.

  2. Follow normal patch procedures for binary replacement but do not start any Oracle GoldenGate processes. See Installing Patches for Oracle GoldenGate Microservices Architecture 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. Using Admin client, 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 EXCLUDEFILTERTABLE object for active/active configurations.

    Caution:

    Do not run the DELETE TRANDATA command as this will cause a data out of sync condition and requires re-initialization.

  5. Manually restart the SQL Server CDC Capture job.

  6. Start the Extract.

Update odbcinst.ini and odbc.ini

If patching Oracle GoldenGate 23.4 or 23.5, to version 23.6 or later, a one-time change to both the odbcinst.ini and odbc.ini is required to force connections to utilize the updated driver supplied with GoldenGate.

You do not need to follow these steps if patching from Oracle GoldenGate 23.6 or after, to later GoldenGate 23ai patch versions.

  1. The odbcinst.ini file is located in the $OGG_HOME/msodbc directory. Modify this file to reflect the information provided below and ensure the ODBC Driver value includes the full path of the Oracle GoldenGate installation. For example: 

    [Microsoft ODBC Driver for SQL Server]
Description=Microsoft ODBC Driver for SQL Server
Driver=/OGG23ai_Install_Path/msodbc/lib64/libmsodbcsql.so

  2. If you have previously created an odbcinst.ini file with DSN entries, update the ODBC Driver value to match that of the Description field in the odbcinst.ini file. It should be set to the following: 

    
Driver=Microsoft ODBC Driver for SQL Server