2 Upgrading Oracle GoldenGate for Big Data

This chapter describes how to upgrade to Oracle GoldenGate for Big Data 12c (12.3.1.2) by downloading the product as described in Downloading Oracle GoldenGate for Big Data, and then choosing the upgrade paths that suits your environment.

After upgrading, you must then convert your Extract processes to Replicat processes.

Note:

There is no supported upgrade path from release 12.1.2 to 12.2.0.x.

There is no supported upgrade path from release 12.2.0.1.0 to 12.2.0.1.1.

Note:

You must upgrade the Cassandra driver to version 3.3.1 if you are using a different version.

Topics:

2.1 Upgrading by Overwriting the Existing Installation

The most straightforward upgrade path is to copy the Oracle GoldenGate for Big Data 12c (12.3.1.x) files into the existing 12c (12.3.1.x or 12.2.0.x) installation directory. Overwriting the product files is possible because there is neither structural nor package name changes in 12.3.1.x. The 12.3.1.x and 12.2.0.x handler and formatter configurations are also compatible with the 12.3.1.x release.

  1. (Source and target systems) Back up the current Oracle GoldenGate for Big Data 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 version 12c (12.3.1.x or 12.2.0.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. Create an installation directory with no spaces in its name.

  5. Extract the ZIP file into this new installation directory, which divides the files into several subdirectories.

  6. Copy the Oracle GoldenGate for Big Data 12c (12.3.1.x) files into the existing 12c (12.3.1.x or 12.2.0.x) installation directory.

  7. Start the Replicat processes and verify that they are running.

    GGSCI> START MANAGER
    GGSCI> START REPLICAT group_name 
    GGSCI> INFO REPLICAT group_name
    GGSCI> VIEW REPORT group_name
    

Certain 12.2.0.x JAR files are still present after the overwriting process though the new 12.3.1.x JAR files are used.

2.2 Upgrading by Installing into a New Directory

Use the following steps to install the Oracle GoldenGate for Big Data 12c (12.3.1.x) files into a new installation directory.

  1. (Source and target systems) Back up the current Oracle GoldenGate for Big Data 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 version 12c (12.3.1.x or 12.2.0.1) 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. Create an installation directory with no spaces in its name.

  5. Extract the ZIP file into this new installation directory, which divides the files into several subdirectories.

  6. In the installation directory, start GGSCI to create the remaining subdirectories in the installation location.

    $ ggsci 
    GGSCI> CREATE SUBDIRS
    
  7. Copy all of the dirprm files from your existing installation into the dirprm directory in the new installation location.

    Note:

    All of your configuration files must be in the dirprm directory. If you have property files, Velocity templates, or other configuration files in a location other than dirprm in your old installation, then you must copy them to the dirprm directory in the new installation.

  8. Copy all of the dirdef files from your existing installation into the dirdef directory in the new installation location.

  9. If you have data files stored in the 12.3.1.x or 12.2.0.x installation dirdat directory, then copy or move the existing trail files to the dirdat directory of the new installation.

  10. If you have additional JAR files or other custom files in your 12.3.1.x or 12.2.0.x installation, then copy them to the new installation directory.

  11. Configure the Replicat processes in the new installation directory by starting GGSCI and adding the Replicat and naming the trails.

    GGSCI> ADD REPLICAT group_name, EXTTRAIL trail_name, ...
    GGSCI> ALTER group_name EXTSEQNO seqno EXTRBA rba
    

    Optionally, you could alter the starting position of Replicat processing as needed.

  12. Start the Replicat processes and verify that they are running.

    GGSCI> START MANAGER
    GGSCI> START REPLICAT group_name 
    GGSCI> INFO REPLICAT group_name
    GGSCI> VIEW REPORT group_name
    
  13. Modify the source system to write to the new Oracle GoldenGate for Big Data installation directory:

    1. (Optional) Upgrade the source database Oracle GoldenGate capture following the upgrade procedure for your database platform.

    2. Configure the source database capture to write to the new Oracle GoldenGate for Big Data 12.3.1.x installation dirdat directory.

    3. When the old Oracle GoldenGate for Big Data installation has processed all its data, switch over to the process that will send data to the new location.

2.3 Switching Existing Extract Processes to Replicat Processes

In previous releases, you could use an Extract and pump process to write to your Big Data targets. In this release, this solution is deprecated so you must use Replicat.

A typical Extract configuration is similar to:

EXTRACT mygroup
SOURCEDEFS path/to/source/def/file
CUSEREXIT libggjava_ue.so CUSEREXIT PASSTHRU INCLUDEUPDATEBEFORES
GETUPDATEBEFORES
TABLE *.*;

With Replicat the preceding configuration would be:

REPLICAT mygroup
SOURCEDEFS path/to/source/def/file
TARGETDB LIBFILE libggjava.so SET property=/path/to/properties/file
MAP *.* TARGET *.*;

The same properties file works in the Replicat configuration so you do not need to change the properties file.

To complete this process, you must add the Replicat group, start the process, and verify that it is running:

GGSCI> ADD REPLICAT group_name, EXTTRAIL trail_name, ...
GGSCI> ALTER group_name EXTSEQNO seqno EXTRBA rbaGGSCI> START REPLICAT group_name 
GGSCI> INFO REPLICAT group_name
GGSCI> VIEW REPORT group_name