Upgrade Tech Stack for OUAW
This page details the tasks required to upgrade the services that are used to run Oracle Utilities Analytics Warehouse.
Note:
Do not change the time zone on the OUAW database server or database instance. The OUAW database server and database instance time zone must always match the source server time zone. Ensure the format of the database time zone (DBTIMEZONE) uses a time zone region name, such as America/New_York. Do not use an absolute offset, such as -05:00.GoldenGate Microservice 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.9.0.0.1 to version 25.10.0.0.0.Note:
Existing GG classic processes need to be cleaned up in both the source and target databases.Clean Up the GoldenGate Processes on the Source Database
- Log in to the source GoldenGate Microservice Administration Service Console.
- Ensure all extract process are stopped. Click the Actions section and choose Delete.
Note:
Execute this process for each primary extract process created for the context code. The primary extract process suffix ends with "X". Once the extract process is unregistered, make sure there is no data in the `DBA_CAPTURE` view in the source database related to this context. Execute the following query in the source database. No results should be displayed.select * from dba_capture where capture_name like '%<contextcode>%'; - Log in to the Source GoldenGate Microservice Distribution Service Console.
- Ensure all distribution paths are stopped. Click the Actions section and choose Delete.
- Check whether the `B1_OGG_SYNC_LOG` table exists in the source. If it does, check whether there is any data in the `B1_OGG_SYNC_LOG` table under the source GoldenGate owner schema. If there is data for `OGG_MODEL_CD`, delete the records related to the instance that should be deregistered.
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; - Optional. If you want to use the same folder structure to update GoldenGate Microservice 19c to 23ai, then rename or remove the existing folders (GoldenGate Home, Service Manager Home, Deployment Home, etc.) that are associated with GoldenGate Microservice 19c.
Clean Up the GoldenGate Processes on the Target Database
- Log in to the target GoldenGate Microservice Administration Service Console.
- Ensure all replicats are in a stopped state. Click the Actions section and choose Delete.
- Ensure that no entry is present in the checkpoint table for replicat processes related to the current context.
Select * from mdadm.b1_checkPoint where group_name like '<context code>%'; - Optional. If you want to use the same folder structure to update GoldenGate Microservice 19c to 23ai, then rename or remove the existing folders (GoldenGate Home, Service Manager Home, Deployment Home, etc.) that are associated with GoldenGate Microservice 19c.
Upgrade the Tech Stack for the Source Database Server
Note:
- 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 install GoldenGate Microservices |
|
| Apply patch for GoldenGate Microservices |
Download and apply patch 38139662 (for Linux) from My Oracle Support.
Note: Find the detailed patch installation steps in the README file within each Patch Package. |
| Create Oracle GoldenGate Microservices Deployment |
Note: OUAW only supports GoldenGate Microservice Secure Deployments.
Prerequisite:
Add Oracle GoldenGate Microservices Deployment with the following command:
Refer to Deploy for more information Examples:
Note: Set the Replication Schema settings.
|
Upgrade the Tech Stack for the Target Database Server
Note:
- 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 apply Database Server Patch |
Download and apply the Database Server Patch 37960098 from My Oracle Support to a temporary directory.
Note: Find the detailed path installation steps in the README file within each Patch Package. |
| Download and install GoldenGate Microservices |
|
| Apply patch for GoldenGate Microservices |
Download and apply patch 38139662 (for Linux) from My Oracle Support.
Note: Find the detailed patch installation steps in the README file within each Patch Package. |
| Create Oracle GoldenGate Microservices Deployment |
Note: OUAW only supports GoldenGate Microservice Secure Deployments.
Prerequisite:
Add Oracle GoldenGate Microservices Deployment with the following command:
Refer to Deploy for more information Examples:
Note: Set the Replication Schema settings.
|
| Download the OUAW database software |
|
| Extract the Admin Tool |
|
Upgrade the Tech Stack for the Target Application Server
Note:
- 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 install the Java Development Kit |
Java 17
|
| Download and install database client |
Download the Oracle Database Client from Oracle Software Delivery Cloud and install it at a customized location. Example: </u01/ouaw/clientBase>
Note: This task is optional if both the OUAW application server and the database server are installed on the same machine. See Install Oracle Database Client for more information. |
| Download and install Oracle Fusion Middleware Infrastructure Patch |
FMW 14c
|
| Download and apply Oracle Fusion Middleware Infrastructure Patch |
FMW/WLS 14c Patches
Note: Do not apply any FMW/WLS 14c patch in this step. Patches will be applied after ODI Domain Upgrade. |
| Download and install Oracle Data Integrator (ODI) |
|
| Download and apply the ODI patch |
Note: Do not apply any ODI 14c patch in this step. Patches will be applied after ODI Domain Upgrade. |
| Download the OUAW Application Software |
|
Upgrade the Existing Domains and Repository
Note:
Before upgrading a repository or domain activity, make sure you have a rollback plan in case it is necessary to revert your changes.ODI Repository and Domain In-Place Upgrades
- For ODI repository and domain in-place upgrades, follow the steps in Upgrading Oracle Data Integrator.
Note:
The ./ua -readiness may fail while running it, generating the exception: "Failed to establish a connection to data source WLSSchemaDataSource" because of the error "UPGAST-00214: Unable to connect to database as the schema user DEV_WLS_RUNTIME". To solve this, it is necessary to follow the steps from the document 2751829, which is available through My Oracle Support. - Download and apply FMW/WLS 14c patches 38166406, 38015961, 38184117, 38032126, and ODI 14c patches 38172533 and 36668195 from My Oracle Support.
Note:
Find the detailed patch installation steps in the README file within each Patch Package.