Upgrading Oracle GoldenGate Microservices – GUI Based

Learn the steps to upgrade Oracle GoldenGate Microservices using the GUI.

To install Oracle GoldenGate Microservices Architecture, refer to

https://docs.oracle.com/en/middleware/goldengate/core/23/coredoc/install-oracle-goldengate.html

At this point, you should have a new Oracle GoldenGate 23ai MA home and any prior release homes of Oracle GoldenGate MA.

Upgrade the Service Manager

After installing the latest Oracle GoldenGate MA version, the next step is to upgrade the Service Manager:

1. Log into Service Manager from the URL: https://hostname:servicemanager_port

2. Expand the ServiceManager link in the Deployments section of the Service Manager Overview page.

3. Click Details and then the pencil icon next to the Deployment Detail section to open the dialog box for editing the GoldenGate home path.

4. Update the GoldenGate Home path with the full path to the new Oracle GoldenGate home.

5. Click Submit.

6. Return to the Deployments section and click the Restart icon in the Actions Field to restart the Service Manager.

Upgrade the Deployment

Deployments can be upgraded in the same step with the Service Manager or they can be upgraded at a later time after the Service Manager has been upgraded.

To upgrade a deployment:

1. Stop all Extract and Replicat processes gracefully:

   • Check for open (long running) transaction and Bounded Recovery as it may take longer to stop Extract gracefully.

   • If any unnecessary open transactions are visible, for example SEND EXTRACT group_name SHOWTRANS, then those transactions can be skipped or immediately forced to stop. In this case, a Bounded Recovery checkpoint can be retrieved using the following command:

     SEND EXTRACT group_name, BR BRCHECKPOINT immediate

2. Verify the current location of Oracle GoldenGate 23ai home directory from Service Manager.
   1. Login to the Service Manager: http://hostname:servicemanager_port
   2. Expand the ServiceManager link in the Deployments section of the Service Manager Overview page.
   3. Copy the GoldenGate Home path.
3. Return to the Deployments section and expand the link of the deployment to be upgraded.
4. Click Details and then edit the deployment’s GoldenGate Home with that of the Oracle GoldenGate 23ai Home directory.
   1. Click the pencil icon next to the Service Manager Deployment Detail.
   2. Update the Oracle GoldenGate Home path with the complete path to the new Oracle GoldenGate home directory.
   3. Click Submit.
   4. Confirm that the Oracle GoldenGate Home path has been updated.
5. On the Service Manager page, select the deployment name from the left navigation pane.
6. Click Configuration to modify the settings for the environment variables, if required.

   Oracle GoldenGate for Oracle Database, with the Unified Build feature requires only the TNS_ADMIN to be adjusted to the Oracle Database Client software within Oracle GoldenGate.

   TNS_ADMIN = Location of tnsnames.ora and sqlnet.ora

   The OGG_HOME environment variable can automatically detect the DATABASE_HOME, LD_LIBRARY_PATH, and JAVA_HOME.

   Note:

   When upgrading from 21c to 23ai, this step is not necessary. If upgrading from Oracle GoldenGate 19c (or earlier) to 23ai, you only need the TNS_ADMIN environment variable.
7. (SQL Server only) Oracle GoldenGate 23ai for SQL Server on Linux includes an ODBC driver for database connectivity. Although it’s not required, it is recommended to utilize the packaged driver. To use the packaged driver, two new environment variables need to be created and any previously created odbc.ini file needs to be updated.

   Add the following environment variables to the deployment:

   • ODBCSYSINI = ${OGG_HOME}/msodbc

   • ODBCINI = ${OGG_HOME}/msodbc/odbc.ini

   After creating the new environment variables, copy your existing odbc.ini file to the GoldenGate msodbc folder and change the ODBC Driver value of any DSN entry to the following:

   Driver=Microsoft ODBC Driver for SQL Server

8. Click Submit to save the changes, then return to the Service Manager Home page.
9. Click the Restart icon in the Actions field for the deployment and click OKto restart the deployment.
10. Log back into the Adminstration Service and start any Extract and Replicats.