Perform Pre-Upgrade Steps

This page details the actions to take before upgrading Oracle Utilities Analytics Warehouse from version 2.8.0.0.1 to version 2.8.0.1.0.

Note: This upgrade path is valid only for source applications certified with both OUAW 2.8.0.0.1 and OUAW 2.8.0.1.0. Source application upgrade is not part of this upgrade path.

Preparation Steps

Notes:

  • Customers need to apply the patch 2.8.0.0.1 with the required tech stack before upgrading from 2.8.0.0.1 to 2.8.0.1.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.

  1. 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.

  2. Make sure that the ODI operator logs are available during and after the upgrade. This can be ensured by increasing the log retention period to 60 days from the Global Configuration page in Apex.
  3. Make sure the ODI log level is set to maximum in Global Configuration. This can be ensured by increasing the ODI log level to 5 or 6 from the Global Configuration page in Apex.
  4. 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);

  5. 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

  6. Stop BI_RUN_ALL from Oracle Data Integrator Studio and follow these steps:
    1.  Log in to Oracle Data Integrator Studio. 
    2. Navigate to Designer > Load plan and Scenarios > Framework > B1_RUN_ALL > Scheduling.
    3. Double-click Global/WLS_AGENT, select Inactive, and save the changes.
    4. On the studio, navigate to the Topology tab.
    5. Right-click OracleDIAgent and select Update Schedule.

  7. Rename the scenario B1_PKG_CF_DAMAGE_ASMT_DETAIL back to B1_PKG_CF_DAMAGE_ASMT_NEW_DETAIL_FROM2401 by following the steps below. (Note: This step is only valid for NMS Application version 2.4.0.1. or later.)

    1. Log in to Oracle Data Integrator Studio.

    2. Navigate to Designer > Load Plans and Scenarios > Oracle Utilities BI > NMS > Facts > New Damage Assessment Detail Fact.

    3. Expand the Fact, right-click on B1_PKG_CF_DAMAGE_ASMT_DETAIL scenario, and select Open.

    4. Navigate to the Definition tab and modify the name of the scenario to B1_PKG_CF_DAMAGE_ASMT_NEW_DETAIL_FROM2401.

    5. Click Save.

  8. 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 above. If any rows are returned, that means jobs are not complete yet. Wait until they are complete.

  9. Stop both the Oracle Data Integrator admin and managed servers.

    Copy
     cd <Domain Home>/<odi_domain>/bin     
     ./stopManagedWeblogic.sh <ODI_server1>     
     ./stopWeblogic.sh

  10. Stop the OAS Services.

    Copy
    cd <Domain Home>/<OAS_domain>/bitools/bin     
    ./stop.sh

  11. Stop the source application. Ensure the database is up and running in both the source and the target.
  12. Stop the GG process EXTRACT from the source and the REPLICATS from the target database server.

    Copy
    cd <Goldengate Home>       
    ./ggsci       
    stop <EXTRACT/REPLICATS> <Context Code>
    stop mgr
    stop jagent

Back to Top