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:

Upgrade the Tech Stack for the 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. 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 (Example: JDK 1.8.0.291) from Oracle Technology Network to a temporary directory.
  2. Upgrade the JDK to JDK 1.8.0 (291).

Download and Upgrade Oracle Database Server Enterprise
  1. Download Oracle Database Server Enterprise Edition 19C from Oracle Software Delivery Cloud to a temporary directory.
  2. Upgrade the database to 19C.

Download and apply Database Server Patch
  1. Download the Database Server Patch 32545013 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
  1. Rename the current GoldenGate Home directory.
  2. Download Oracle GoldenGate 19.1 from Oracle Software Delivery Cloud to a temporary directory. See Install GoldenGate for details.
  3. Install Oracle GoldenGate onto a customized location on the target database server. This location should have the same directory name as the previously installed GolgenGate Home.

    Example: /u01/ouaw/goldengate

    Note: This location will be referred to as Oracle GoldenGate Home.

Download and install GoldenGate Monitor Agent

GoldenGate Monitor Agent Installation Steps:

  1. Rename both the GoldenGate Monitor Agent and the GoldenGate Monitor Agent instance homes.
  2. Download Oracle GoldenGate Monitor Agent 12.2.1.2 from Oracle Software Delivery Cloud to a temporary directory.
  3. Choose "Oracle GoldenGate Monitor Agent" as the installation type when installing onto a customized location. Use the same directory name as for the previously installed GolgenGate Monitor Agent home.

    Example: </u01/ouaw/oggagent>

    Note: This location will be referred to as Oracle GoldenGate Monitor home.

Apply patch for GoldenGate Monitor Agent

  1. Download and apply patch 26982776 from My Oracle Support to Oracle GoldenGate Monitor Agent.

  2. Set the ORACLE_HOME to Oracle GoldenGate Monitor agent home installed location.

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

    Copy
    $ORACLE_HOME/OPatch/opatch apply

GoldenGate Monitor Agent Configuration

Edit the configuration template:

  1. Go to <Oracle GoldenGate Monitor Agent home>/oggmon/ogg_agent/cfg_templates directory and open the Config.properties file.

  2. Modify the parameters using the followiing values:

    ACTUAL : jagent.host=localhost
    CHANGE TO : jagent.host=<<actual hostname on which Oracle GoldenGate is installed>>

    ACTUAL: monitor.jmx.username=oggmsjmxusr
    CHANGE TO: monitor.jmx.username=jmx_src

    ACTUAL: jagent.username=oggmajmxusr
    CHANGE TO: jagent.username=<<Oracle GoldenGate software installed OS user>>

    ACTUAL: jagent.rmi.port=5559
    CHANGE TO: jagent.rmi.port=5557 (or any free port other than the one on which the rmiregistry is started)

    ACTUAL: agent. type.enabled=OGGMON
    CHANGE TO : agent.type.enabled=OEM

Create GoldenGate Monitoring Agent instance:

  1. Navigate to <Oracle GoldenGate Monitor home>/oggmon/ogg_agent.

  2. Run the createMonitorAgentInstance.sh script. Example execution:

    Copy 
    cd <Oracle GoldenGate Monitor home>/oggmon/ogg_agent
    ./createMonitorAgentInstance.sh
                                        
  3. When prompted, enter the following information:
    • Oracle GoldenGate home directory: <GoldenGate Home location>
    • Path to be used for Oracle GoldenGate Monitor Agent instance.

      Example: </u01/ouaw/ogginstance>.

      Note: This will be referred to as the Oracle GoldenGate Monitor Instance home.

    • A unique name to replace the timestamp in the name of the file used to start the Oracle GoldenGate Monitor agent instance.

Create JAgent wallet:

  1. Navigate to <Oracle GoldenGate Monitor Agent instance Home>/bin.
  2. Add JAVA_HOME/bin to the PATH variable.

    Copy
    export ORACLE_HOME=<ORACLE HOME>
    export PATH=$ORACLE_HOME/bin:$PATH

  3. Run the pw_agent_util.sh script. Example execution:

    Copy
    cd  < Oracle GoldenGate Monitor Instance>/bin
    ./pw_agent_util.sh -jagentonly                                

  4. Enter the Oracle wallet password. This password has to be entered as the password for the JAgent while running the OUAW installer.

  5. Store the password for future reference.

Set Up Oracle GoldenGate
  1. Connect to the target database as a sys user and run the following command:

    Copy
    alter system set enable_goldengate_replication=TRUE scope=both;

  2. In the command window, navigate to the Oracle GoldenGate Home directory.

  3. Edit the GLOBALS file in the directory and add the following command: EnableMonitoring. Save the file.

  4. Navigate to GoldenGate home and check for directories (dirprm,dirdat,dirrpt,...,). If these directories do not exist, connect to ggsci prompt and execute the statement below. This will create all required directories for the GoldenGate configuration.

    Copy
    export ORACLE_HOME=<ORACLE HOME>
    export PATH=$ORACLE_HOME/bin:$PATH
    ./ggsci
    CREATE SUBDIRS
    start mgr

Configure and Start GoldenGate JAgent

Note: Perform the following steps in case rmiregistry services are not running. Use the same RMI Registry port that was used before upgrade.

  1. Start the rmiregistry services using these commands:

    Copy
    set JAVA HOME and PATH
    export JAVA_HOME=<JAVA_HOME>
    export PATH=$JAVA_HOME/bin:$PATHr
    miregistry <port number> &

    Example: rmiregistry 5559 &

  2. Navigate to <GoldenGate Home>/dirprm  and edit the jagent.prm file. Replace COMMAND java  with COMMAND <JAVA_HOME>/bin/java . 

  3. Navigate to <GoldenGate Home>  and run the command below. 

    Copy
    export ORACLE_HOME=<ORACLE_HOME>
    export PATH=$ORACLE_HOME/bin:$PATH 
    ./ggsci
    START JAGENT  

Back to Top

Upgrade the Tech Stack for the 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 (Example: JDK 1.8.0.291) from Oracle Technology Network to a temporary directory.
  2. Upgrade the JDK to JDK 1.8.0 (291)

Download and Upgrade the database client

Download the Oracle Database Client 19C from Oracle Software Delivery Cloud and Upgrade Oracle Database Client to 19C.

Note: This task is optional if both the OUAW application and database servers are installed on the same machine. See Install Oracle Database Client for more information.

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 at a customized location.

    Example: </u01/ouaw/middleware>.

    Note: This will be referred to as FMW Home. This installation path can be used for Oracle Data Integrator's ORACLE_HOME as well as for Oracle Analytics Server (OAS) installations.

See Install Oracle Fusion Middleware Infrastructure for more information.

Download and apply Oracle Fusion Middleware Infrastructure Patch

  1. Download the Oracle Fusion Middleware Infrastructure Patch 30657796 (available inside OAS 5.9 package) from Oracle Software Delivery Cloud to a temporary directory.
    Example: </u01/ouaw/temp/middleware>.

  2. Unzip the patch and navigate to the patch top folder.

  3. Run the following:

    Copy
    $ORACLE_HOME/OPatch/opatch apply

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

Download and install Oracle Analytics Server (OAS)
  1. Download the latest Oracle Analytics Server (OAS) version (5.9.0) from Oracle Software Delivery Cloud to a temporary directory.

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

  2. 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 install Oracle Data Integrator (ODI)
  1. Download Oracle Data Integrator(ODI) 12.2.1.4 from Oracle Software Delivery Cloud to a temporary directory.

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

  2. Extract and install ODI at the ORACLE_HOME location at same as FMW Home path.

    Example: </u01/ouaw/middleware>.

    After installation, you can find the ODI directory under the FMW Home path.

    Example: <FMW Home>/odi. If necessary, see Install Oracle Data Integrator for detailed instructions.

Download and apply the ODI patch
  1. Download and apply the Opatch from My Oracle Support for Oracle Data Integrator 12.2.1.4 patch 31510501.
  2. Unzip the patch and navigate to the patch top folder.
  3. Run the following executable:

    Copy
     $ORACLE_HOME/OPatch/opatch apply

Back to Top

Upgrade the Existing Domains and Repository (ODI, Apex, and OAS)

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. Additionally, all domains should be in the "stopped" state before the upgrade.

ODI Repository and Domain In-Place Upgrades

For the ODI repository and domain in-place upgrades, follow the steps on Upgrading Oracle Data Integrator.

Note: Before starting the ODI admin and managed server, perform the following steps to avoid issues in the source configuration. See My Oracle Support doc ID: 2785415.1 for more information.

Modify the setDomainEnv.sh script for ODI agent connectivity

  1. In the command shell, change the directory to ODI Domain Home.

    Example: cd <odi_domain>/bin

  2. Add the -Dweblogic.oif.serialFilterScope=weblogic argument to setDomainEnv.sh immediately below an existing JAVA_OPTIONS command.

    Example: JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.oif.serialFilterScope=weblogic"

    Detail of the script where the mentioned argument is being added after the Java Options command.

Modify the startweblogic.sh script for ODI agent connectivity

  1. Create a backup of the startweblogic.sh script.
  2. Open the startweblogic.sh script in the editor.
  3. Add the following code after the pattern # START WEBLOGIC.

    Copy
    export CONFIG_JVM_ARGS="-Djava.security.egd=file:/dev/./urandom -Dweblogic.security.SSL.enableJSSE=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust -Dweblogic.security.CustomTrustKeyStoreType=JKS"

  4. Insert the following code after the pattern Djava.security.policy=${WLS_POLICY_FILE }:

    Copy
    -Djava.security.egd=file:/dev/./urandom -Dweblogic.security.SSL.enableJSSE=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust -Dweblogic.security.CustomTrustKeyStoreType=JKS

    Note: Insert the code in all three places where the pattern appears.

    Here is how the code looks before inserting the above code lines:
    ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${LAUNCH_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WLS_POLICY_FILE} ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}

    Here is how the code should look after inserting the above code lines:
    ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} ${LAUNCH_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WLS_POLICY_FILE} -Djava.security.egd=file:/dev/./urandom -Dweblogic.security.SSL.enableJSSE=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust -Dweblogic.security.CustomTrustKeyStoreType=JKS ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}

Back to Top

OAS Repository and Domain In-Place Upgrades

For the OAS/OBIEE repository and the domain in-place upgrades, follow the steps on Upgrading Oracle Analytics Server.

Note: After upgrading to Oracle Analytics Server (OAS), the Cluster Controller (obiccs) may fail to start. Set Cluster Enabled tag to true if it was set to false in [DOMAIN_HOME]/config/fmwconfig/biconfig/OBICCS/bi-cluster-config.xml file. To solve the issue, follow the steps on document 2685095.1 on My Oracle Support.

Apex Domain In-Place Upgrade

The same steps that were used for upgrading the OAS domain will be used for the Apex domain in-place upgrade, with the exception of the step for Upgrading Product Schemas. Product schemas/RCU schema are not present in this Apex domain. See Upgrading Oracle Analytics Server for details.

Back to Top