Prerequisites

Before performing the upgrade procedure, read the Release Notes for Oracle GoldenGate to determine whether the new release affects the following in your configuration:

New default process behavior.
Parameters that changed or were deprecated.
Parameters that were added to support a desired new feature or database type.
Parameter default values that have changed.
New data type support that might require changes to TABLE or MAP statements.
Interaction with native database components that might require database change.

As a best practice, perform a minimal upgrade first, so that you can troubleshoot more easily in the event that any problems arise. When you verify that your environment is upgraded successfully, you can implement the new functionality.

When upgrading your database and Oracle GoldenGate simultaneously, you must upgrade the database first. However, ensure that the Oracle GoldenGate version is equal to or higher than the database version.

For Oracle Database, if you are using symbolic links that point to the Oracle GoldenGate directories, such as dirprm and dirdat, you need to use the parameter ALLOWOUTPUTDIR within GLOBALS.

You can prevent startup delays that can cause lag by having any required parameter changes made ahead of time, so that they are ready when you restart the processes. You should not make parameter changes while a process is running, but you can:

Make a copy of the parameter file.
Make edits to the copy.
After you shut down the processes during the upgrade procedure, copy the old parameter file to a new name (to save it as backup).
Copy the new parameter file to the old parameter file's name.

Take into account the following pre-upgrade requirements:

Only if the trail file format is being changed, allow the Oracle GoldenGate processes to finish processing all current DML and DDL data in the Oracle GoldenGate trails.
When upgrading your database and Oracle GoldenGate simultaneously, you must upgrade the database first.