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 apply Database Server Patch |
Note: Follow the README while applying the database patches. |
Apply patch for GoldenGate |
Note: Do not start the GoldenGate processes after applying the patch. |
Apply patch for GoldenGate Monitor Agent |
|
Download and extract Oracle APEX |
Note: This location will be referred to as the New APEX Home directory. |
Download the OUAW database software |
Note: You can find the OUAW Database Installers at the following location after unzipping the file: </u01/ouaw/temp/database/BI2802> |
Extract the Admin Tool |
|
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 |
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 |
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).
Note: ORACLE_HOME is referred to as <FMW Home location>. |
Download and install Oracle Analytics Server (OAS) |
Example: </u01/ouaw/temp/oas>. |
Download and apply Oracle Analytics Server (OAS) Patch |
Note: Apply this patch in OAS ORACLE_HOME (FMW Home).
|
Download and apply ODI Patches |
Note: Apply this patch in ODI ORACLE_HOME (FMW Home).
Post Patch Instructions: Note: For more details, follow the README file in patch package.
Note: Before performing this upgrade, make sure that all work and master repository schema users have been granted CREATE VIEW and CREATE PROCEDURE privileges.
Copy
|
Download and Extract APEX |
Download Oracle APEX 22.1 from Oracle Application Express to a local directory. Example: </u01/ouaw/apex> After extraction, you can see the apex folder. Example: </u01/ouaw/apex/apex> |
Download the OUAW Application Software |
|
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.