Perform Pre-Upgrade Steps
This page details the actions to take before upgrading Oracle Utilities Analytics Warehouse from version 2.7.0.1.3 to version 2.8.0.2.0.
Notes:
- Customers need to upgrade to the latest supported tech Stack on 2.7.0.1.3 (for example: DB19c). See section Supported Platforms and Hardware Requirements in the Installation Guide 2.7.0.1 before performing the upgrade activities from 2.7.0.1.3 to 2.8.0.2.0.
- Before proceeding with the prerequisite steps on the target and the source database servers, ensure you have a rollback plan in case it is necessary to revert the changes.
-
Ensure that data in the source is in sync with the replication tables.
Note: The Lag for Chkpt and Time Since Chkpt in both the source and target databases should be 0.
-
Make sure that the ODI operator logs are available during and after the upgrade.
Note: This can be ensured by increasing the log retention period to 60 days from the Global Configuration page in Apex.
- Make sure the ODI log level is set to maximum in Global Configuration.
Note: This can be ensured by increasing the ODI log level to 5 or 6 from the Global Configuration page in Apex.
-
Make sure that the primary keys of all replication tables are present. Use the following query to retrieve the tables that have the primary key missing.
Copy
SELECT * FROM MDADM.B1_SOURCE_TABLE S WHERE PROD_FLG = '<configured source product value>' AND BASE_REPLICATE_FLG ='Y'
AND NOT EXISTS (SELECT 1 FROM ALL_CONSTRAINTS C WHERE CONSTRAINT_TYPE ='P' AND OWNER='<replication schema name for configured source>' AND S.TBL_NAME=C.TABLE_NAME); - Log in to Oracle Utilities Analytics Warehouse ODI server and start the ODI client.Copy
export JAVA_HOME=<JAVA HOME>
export PATH=$JAVA_HOME/bin:$PATH
cd <FMW Home>/odi/studio
./odi - Stop BI_RUN_ALL. from ODI studio and follow these steps:
- Log in to Oracle Data Integrator Studio.
- Navigate to Designer > Load plan and Scenarios > Framework > B1_RUN_ALL > Scheduling.
- Double-click Global/WLS_AGENT, select Inactive, and save the changes.
- On the studio, navigate to the Topology tab.
- Right-click OracleDIAgent and select Update Schedule.
- Run the following query from the target database server to check if all jobs are complete.
Copy
SELECT * FROM mdadm.b1_jobs_vw WHERE status_flg in ('W','P','R');
Note: No rows should be returned from the query mentioned above. If any rows are returned, that means jobs are not yet completed. Wait until they complete.
- Stop both Oracle Data Integrator admin, and managed servers.
Copy
cd <Domain Home>/<odi_domain>/bin
./stopManagedWeblogic.sh <ODI_server1>
./stopWeblogic.sh - Stop the OAS services:Copy
cd <Domain Home>/<OAS_domain>/bitools/bin
./stop.sh - Stop Apex admin and managed servers.
Copy
cd <Domain Home>/<apex_domain>/bin
./stopManagedWebLogic.sh <apex_server1>
./stopWebLogic.sh - Stop the source application. Ensure the database is up and running in both the source and the target.