Upgrade Tech Stack for OUAW

This page details the tasks required to upgrade the services that are used to run Oracle Utilities Analytics Warehouse.

On this page:

GoldenGate Classic Processes Cleanup

Warning: GoldenGate processes cannot be rolled back once these have been cleaned up. Perform the GoldenGate process cleanup only if you have decided to upgrade Oracle Utilities Analytics Warehouse from version 2.8.0.0.1 to version 2.9.0.0.0.

Note: Existing GG classic processes need to be cleaned up in both the source and target databases.

Clean Up the GG Processes on the Source Database

  1. On the source database, log in to the GG command line interface (ggsci prompt).

  2. Stop all extract and pump processes associated to this instance if they are not already stopped.

  3. Unregister the primary extract processes on the source system related to this context.

    Copy
    GGSCI> dblogin userid <gguser name>, password <Password>
    GGSCI> unregister extract <primary extract name> database

    Note: Run this command for each primary extract process created for context code. Primary extract process suffix with "X" and pump extract process suffix with "P". Once the extract process is unregistered, make sure that there is no data related to this context in the source database's DBA_CAPTURE view.

    Run this query in the source database and verify that no results are displayed.

    Copy
    select * from dba_capture where capture_name like '%<contextcode>%';

  4. Delete each one of the instance's extract and pump processes.

    Copy
    GGSCI> Delete extract <extract and pump process name>

  5. Clean up all trail files present in <Source GG Home>/dirdat/<Context Code>.

  6. Clean up all instance-related checkpoint files present in <Source GG Home>/dirchk/.

  7. Clean up all context-related report files present in <Source GG Home>/dirrpt/.

  8. Clean up all context-related temporary files present in <Source GG Home>/dirtmp.

  9. Clean up all context-related obey files present in <Source GG Home>/diroby/.

  10. Clean up all context-related parameter files present in <Source GG Home>/dirrpm/.

    Note: Do not modify or remove any other parameter file. For example, do not modify or remove manager.prm or jagent.prm. But the manager and jagent param files can be removed if you opt to uninstall Goldengate Classic.

  11. Check if there is any data in the source GG owner schema B1_OGG_SYNC_LOG table.

    If there is data for OGG_MODEL_CD, delete the records pertaining to the instance that is to be de-registered.

    Copy
    select OGG_MODEL_CD FROM <GG Owner Schema>.B1_OGG_SYNC_LOG WHERE OGG_MODEL_CD like '<context code>%';
    DELETE FROM <GG Owner Schema>.B1_OGG_SYNC_LOG WHERE OGG_MODEL_CD like '<context code>%';
    COMMIT;

Clean Up the GG Processes on the Target Database

  1. On the target database, log in to the GG command line interface (ggsci prompt).

  2. Stop all replicat processes associated to this context if they are not already stopped.

  3. Log in to the database by using the DBLOGIN command from the GGSCI command prompt.

    Use the DBLOGIN credential from the <Context Code>.oby file that is located in the <Goldengate Home>/dirtmp directory.

  4. Delete from the target system all replicat processes related to this context.

    Copy
    GGSCI> Delete replicat <replicat process name>

  5. Clean up all trail files present in <Source GG Home>/dirdat/<Context Code>.

  6. Clean up all instance-related checkpoint files present in <Target GG Home>/dirchk/.

  7. Clean up all context-related report files present in <Target GG Home>/dirrpt/.

  8. Clean up all context-related temporary files present in <Target GG Home>/dirtmp.

  9. Clean up all context-related obey files present in <Target GG Home>/diroby/.

  10. Clean up all context-related parameter files present in <Target GG Home>/dirrpm/.

    Note: Do not modify or remove any other parameter file. For example, do not modify or remove manager.prm or jagent.prm. But the manager and jagent param files can be removed if you opt to uninstall Goldengate Classic.

  11. Ensure that no entry is present in the checkpoint table for the replicat processes related to the current context.

    Copy
    Select * from mdadm.b1_checkPoint where group_name like '<context code>%';

Back to Top

Upgrade the Tech Stack for the Source Database Server

This section covers the instructions for the downloads, installations, and upgrades that can be performed on the source database server.

Notes:

  • Before upgrading, back up the current environment and ensure you have a rollback plan.
  • Make sure the same OS user installs all software, and that you replace all parameters enclosed in <> with valid values.
  • While the table below includes some directory structures as examples, you can choose where to install the software.

Task

Description

Download and Upgrade the Java Development Kit

  1. Download the Oracle Java Development Kit (JDK) 1.8 version (JDK 1.8.0.411) from Oracle Technology Network to a temporary directory.
  2. Upgrade the JDK to JDK 1.8.0 (411).

    Note: Rename the existing JDK path and upgrade/install the new JDK by creating the same JDK path so that JAVA_HOME is the same as the previous.

Download and install GoldenGate Microservices

  1. Download Oracle GoldenGate Microservices 19.1 from Oracle Software Delivery Cloud to a temporary directory. See Installing Oracle GoldenGate Microservices for details.

    Example: </u01/ouaw/temp/goldengate>

  2. Install Oracle GoldenGate Microservices on the Target Database server(s) at a customized location.

    Example: </u01/ouaw/goldengate_MA>.

    This will be referred to as Oracle GoldenGate Microservices Installation Home.

Apply patch for GoldenGate Microservices
  1. Download and apply patch 36238786 (for Linux) or 36176781 (for Solaris and AIX) from My Oracle Support on top of the Oracle GoldenGate Microservices.
  2. Set the ORACLE_HOME to the Oracle GoldenGate Microservices home installed location. 
  3. Unzip the patch, navigate to the patch top folder, and run the following:

    Copy
    $ORACLE_HOME/OPatch/opatch apply

Create Oracle GoldenGate Microservices Deployment

Note: OUAW only supports GoldenGate Microservice Secure Deployments.

Prerequisites:

  • Ensure you have Root CA Certificates, Server Certificates, Client Certificates for Distribution (Source) and Receiver (Target) GoldenGate Microservices Servers and create the trust between the Certificates before Oracle GoldenGate Microservices Deployment. See more details for Self-Signed Certificates.
  • Ensure you have created respective wallets for Distribution (Source) and Receiver (Target) GoldenGate Microservices.

Add Oracle GoldenGate Microservices Deployment with the following command:

Copy
<Oracle GoldenGate Microservices Installation Home>/bin/oggca.sh

Refer to Setting Up Secure or Non-Secure Deployments for more information

Examples:

  • </u01/ouaw/goldengate_SM> - This will be referred to as Oracle GoldenGate Microservices Service Manager Home.
  • </u01/ouaw/goldengate_Deploy> - This will be referred to as Oracle GoldenGate Microservices Deployment Home.

Note:

  1. Set the security options by selecting the SSL/TLS security checkbox and defining the respective wallets.

  2. Set the replication settings.
    • Set the Default Schema to the Oracle GoldenGate Owner like C##GGOWNER for the Distribution (Source) GoldenGate Microservices. Do not create a new GoldenGate Owner. Use the same user that was used in GoldenGate Classic Source configuration.

Back to Top

Upgrade the Tech Stack for the Target Database Server

This section covers the instructions for the downloads, installations, and upgrades that can be performed on the Oracle Utilities Analytics Warehouse database server.

Notes:

  • Before upgrading, back up the current environment and ensure you have a rollback plan.
  • Make sure the same OS user installs all software, and that you replace all parameters enclosed in <> with valid values.
  • While the table below includes some directory structures as examples, you can choose where to install the software.

Task

Description

Download and Upgrade the Java Development Kit

  1. Download the Oracle Java Development Kit (JDK) 1.8 version (JDK 1.8.0.411) from Oracle Technology Network to a temporary directory.
  2. Upgrade the JDK to JDK 1.8.0 (411).

    Note: Rename the existing JDK path and upgrade/install the new JDK by creating the same JDK path so that JAVA_HOME is the same as the previous.

Download and apply Database Server Patch

  1. Download the Database Server Patch 35943157 from My Oracle Support to a temporary directory.

    Example: </u01/ouaw/temp/database>.

  2. Export the ORACLE_HOME set to the Database Server installed path. 

  3. Unzip the patch, navigate to the patch top directory, and run the following:

    Copy
    $ORACLE_HOME/OPatch/opatch apply

Download and install GoldenGate Microservices

  1. Download Oracle GoldenGate Microservices 19.1 from Oracle Software Delivery Cloud to a temporary directory. See Installing Oracle GoldenGate Microservices for details.

    Example: </u01/ouaw/temp/goldengate>

  2. Install Oracle GoldenGate Microservices on the Target Database server(s) at a customized location.

    Example: </u01/ouaw/goldengate_MA>.

    This will be referred to as Oracle GoldenGate Microservices Installation Home.

Apply patch for GoldenGate Microservices
  1. Download and apply patch 36238786 (for Linux) or 36176781 (for Solaris and AIX) from My Oracle Support on top of the Oracle GoldenGate Microservices.
  2. Set the ORACLE_HOME to the Oracle GoldenGate Microservices home installed location. 
  3. Unzip the patch, navigate to the patch top folder, and run the following:

    Copy
    $ORACLE_HOME/OPatch/opatch apply

Create Oracle GoldenGate Microservices Deployment

Note: OUAW only supports GoldenGate Microservice Secure Deployments.

Prerequisites:

  • Ensure you have Root CA Certificates, Server Certificates, Client Certificates for Distribution (Source) and Receiver (Target) GoldenGate Microservices Servers and create the trust between the Certificates before Oracle GoldenGate Microservices Deployment. See more details for Self-Signed Certificates.
  • Ensure you have created respective wallets for Distribution (Source) and Receiver (Target) GoldenGate Microservices.

Add Oracle GoldenGate Microservices Deployment with the following command:

Copy
<Oracle GoldenGate Microservices Installation Home>/bin/oggca.sh

Refer to Setting Up Secure or Non-Secure Deployments for more information

Examples:

  • </u01/ouaw/goldengate_SM> - This will be referred to as Oracle GoldenGate Microservices Service Manager Home.
  • </u01/ouaw/goldengate_Deploy> - This will be referred to as Oracle GoldenGate Microservices Deployment Home.

Note:

  1. Set the security options by selecting the SSL/TLS security checkbox and defining the respective wallets.

  2. Set the replication settings.
    • Set the Default Schema to MDADM for the Receiver (Target) GoldenGate Microservices.

Download and extract Oracle APEX

  1. Download the latest version of Oracle APEX 23.2 from Oracle APEX to a local directory.

    Example: </u01/ouaw/apex>.

  2. Extract the APEX installer into customized location.

    Example: </u01/ouaw/apex>

    This location will be referred to as the APEX Home directory.

Download the OUAW database software

  1. Download "Oracle Utilities Analytics Warehouse v2.9.0.0 Oracle Database Multiplatform.zip" from Oracle Software Delivery Cloud.

  2. Unzip the file to a temporary directory using any zip command. Example: </u01/ouaw/temp/database>.

Note: You can find the OUAW Database Installers at the following location after unzipping the file:
</u01/ouaw/temp/database/BI2900>

Extract the Admin Tool

  1. Download "Oracle Utilities Analytics Warehouse v2.9.0.0 Multiplatform.zip" from Oracle Software Delivery Cloud.

  2. Extract "Oracle Utilities Analytics Warehouse v2.9.0.0 Multiplatform.zip" AdminTool folder to a temporary directory. Example: </u01/ouaw/temp/AdminTool>. This directory contains database SQL scripts.

Back to Top

Upgrade the Tech Stack for the Target Application Server

This section covers the instructions for the downloads, installations, and upgrades that can be performed on the Oracle Utilities Analytics Warehouse application server.

Notes:

  • Before upgrading, back up the current environment and ensure you have a rollback plan.
  • Make sure the same OS user installs all software, and that you replace all parameters enclosed in <> with valid values.
  • While the table below includes some directory structures as examples, you can choose where to install the software. Make sure to keep track of all the home directories you create, as these will be used for OUAW installation.

Task

Description

Download and Upgrade the Java Development Kit

  1. Download the Oracle Java Development Kit (JDK) 1.8 version (JDK 1.8.0.411) from Oracle Technology Network to a temporary directory.
  2. Upgrade the JDK to JDK 1.8.0 (411).
  3. Note: Rename the existing JDK path and upgrade/install the new JDK by creating the same JDK path so that JAVA_HOME is the same as the previous.

Download and install Oracle Fusion Middleware Infrastructure

  1. Download the Oracle Fusion Middleware Infrastructure 12.2.1.4 from Oracle Software Delivery Cloud to a temporary directory.
    Example: </u01/ouaw/temp/middleware>.

  2. Install the software in a customized location.

    Example: </u01/ouaw/middleware>.

    Note: This will be referred to as FMW Home. This installation path can be used for Oracle Analytics Server 7.6 (OAS 2024).

  3. See Install Oracle Fusion Middleware Infrastructure for more information.

Download and apply Oracle Fusion Middleware Infrastructure Patch

Note: Apply these patches in both OAS and ODI ORACLE_HOME (FMW Home).

  1. Download the Oracle WebLogic Server 12.2.1.4 Patch 34065178 (required FMW Compatibility Patch for JDK 8 u331 or later) and 36178496 from My Oracle Support to a temporary directory.

    Example: </u01/ouaw/temp/middleware>

    Note: Detailed patch installation steps are in the README file in each patch package.

  2. Unzip the patch and navigate to the patch top folder.
  3. Run the following to install patch 34065178:

    Copy
    $ORACLE_HOME/OPatch/opatch apply

  4. Run the following to install patch 36178496:

    Copy
    $ORACLE_HOME/OPatch/opatch napply -oh <ORACLE_HOME> -phBaseFile generic_patchlist.txt

  5. Download the Oracle Fusion Middleware Infrastructure 12.2.1.4 36074941, 34809489, 36034300, 35868571, 34542329, and 33950717 patches from My Oracle Support to a temporary directory.

    Example: </u01/ouaw/temp/middleware>

  6. Run the following to install those patches:

    Copy
    $ORACLE_HOME/OPatch/opatch apply

  7. Note: ORACLE_HOME is referred to as <FMW Home location>.

Download and install Oracle Analytics Server (OAS)

  1. Download Oracle Analytics Server version 7.6 (OAS 2024) from Oracle Software Delivery Cloud to a temporary directory.
  2. Example: </u01/ouaw/temp/oas>.

  3. Install the OAS software at the <FMW Home> location. Here consider the ORACLE_HOME path.

    Example: </u01/ouaw/middleware>

    After installation, you can find the "bi" directory inside the FMW Home.

    Example: <FMW Home>/bi

    See Install Oracle Analytics Server for more information.

Download and apply ODI Patches

Note: Apply this patch in ODI ORACLE_HOME (FMW Home).

  1. Download and apply Oracle Data Integrator 12.2.1.4 patch 36114577 from My Oracle Support.
  2. Unzip the patch and navigate to the patch top folder.

  3. Run the following:

    Copy
    $ORACLE_HOME/OPatch/opatch apply

Note: For post patch instructions, follow the README file in patch package.

Download and Extract APEX

Download Oracle APEX 23.2 from Oracle Application Express and it to a local directory.

Example: </u01/ouaw/apex>

After extraction, you can see the apex folder.

Example: </u01/ouaw/apex/apex>

Download and Extract ORDS

Download the Oracle REST Data source (ORDS) 21.4.3 version from Oracle REST Data Services Download  and extract it to a local directory.

Example: </u01/ouaw/ords>

After extraction you can see the ords folder.

Example: </u01/ouaw/ords>

Download the OUAW Application Software
  1. Download the Oracle Utilities Analytics Warehouse v2.9.0.0 Multiplatform.zip and Oracle Utilities Analytics Warehouse v2.9.0.0 Dashboard Component.zip files from Oracle Software Delivery Cloud.

  2. Extract Oracle Utilities Analytics Warehouse v2.9.0.0 Multiplatform.zip and Oracle Utilities Analytics Warehouse v2.9.0.0 Dashboard Component.zip files to a temporary directory.

    Example: </u01/ouaw/temp/application>.

    Note: The ETL Component installer jar file is OUAW_2.9.0.0.0_ETL_generic.jar and the Dashboard Components are <OAS Version>/rpd, catalog, WriteBackTemplates.

Back to Top

Upgrade the Existing Domains and Repository

This section details how to upgrade the existing domains and the repository in accordance with the in-place upgrade domain strategy.

Note: Before upgrading a repository or domain activity, make sure you have a rollback plan in case it is necessary to revert your changes.

OAS Repository and Domain In-Place Upgrades

For OAS repository and domain in-place upgrades, follow the steps in Upgrading to the Latest Release of Oracle Analytics Server.

Note: The ./reconfig.sh may fail while running it, generating the exception: " CFGFWK-60953: An error in reconfiguration template resulted in the following deployment being left in the original MW home: log4j.jar#1.3@1.2.15". To solve this, follow the steps in the document 2933574.1 available on My Oracle Support.

Back to Top