Upgrade Source Applications

This page describes how to upgrade your source applications to be compatible with Oracle Utilities Analytics Warehouse v2.8.0.2.0.

Notes:

  • Before proceeding with the prerequisite steps on the source database server, ensure you have a proper backup plan to revert the changes in case of any failure.
  • Upgrade the source applications to be compatible with Oracle Utilities Analytics Warehouse v2.8.0.2.0.

On this page:

Upgrade Network Management System (NMS) Source Application

Note: Perform the following steps only if the upgraded source application is NMS, and you are upgrading to version 2.6.0 or later.

  1. Ensure the source application is down.

  2. Ensure the database is up and running in both the source and the target.

  3. Ensure the Golden Gate Processes (Extracts and Replicats) are up and running in the source and the target, respectively.

    Note: Make sure that the pump processes transfer all the changes to the target server. The Lag at the Chkpt and Time Since Chkpt should be 0. This can be confirmed by using the info all command after connecting to the ggsci prompt.

  4. Upgrade the NMS source application only—without executing NMS UTC data conversion migration scripts, and without executing the normal setup process which runs other migrations involving DDL changes.

  5. After a successful upgrade, do not release the source applications to end users. Ensure that you stop the source applications but keep the source databases up and accessible.

  6. If the source database is not in UTC, then do the following:

    1. Stop all Golden Gate Processes (EXTRACTS and REPLICATS in the source and the target).

    2. Execute the NMS UTC data conversion migration script as part of the upgrade to NMS 2.6.0.1 before changing the source database time zone to UTC.

    3. Update the source database time zone to UTC as part of the upgrade to NMS 2.6.0.1.

  7. If the source database is in UTC and the source Application is not in UTC, perform the following steps; otherwise perform Step 8:

    1. Alter the initial checkpoint of the Golden Gate EXTRACT & PUMP processes using BEGIN NOW in the source.
      Copy
      GGSCI > ALTER EXTRACT <NMS1>AAX BEGIN NOW
      GGSCI > ALTER EXTRACT <NMS1>AAP BEGIN NOW

      Note: Here the product context code is <NMS1>.

    2. Ensure the source application is still down, and then start all Golden Gate Processes (EXTRACTS and REPLICATS) in the source and target.

  8. If both the source database and source Application are in UTC, ensure the source application is still down, and then start all Golden Gate Processes (EXTRACTS and REPLICATS) in the source and target.

  9. Execute the normal setup process which runs other migrations involving DDL changes as part of upgrade to NMS 2.6.0.1.

  10. Ensure that the table NMS_ACCOUNTS_HISTORY is created in the source database.

  11. Ensure Incremental Changes (DDL and DML changes during the upgrade) are synced. The Lag for Chkpt and Time Since Chkpt in both the source and target databases should be 0.

  12. Stop all Golden Gate Processes (EXTRACTS, REPLICATS, PMSRVR, JAGENT, MANAGER) in the source and the target.

  13. Download and apply Golden Gate patch 35580180 (for Solaris and Linux) or 35682480 (for AIX) and Oracle GoldenGate Monitor Agent patch 34362913 on Source Side.

    Note: Do not start any GoldenGate processes after applying the patch.

  14. Bring up the source application.

Back to Top

Upgrade Other Source Applications

Note: Perform the following steps if the upgraded source applications are Meter Data Management (MDM), Customer Care and Billing (CCB), Customer to Meter (C2M), Work and Asset Management (WAM), and NMS versions below 2.6.0.

  1. Bring down the source application.

  2. Ensure the database is up and running in both the source and the target.

  3. Ensure the Golden Gate Processes (Extracts and Replicats) are up and running in the source and the target, respectively.

    Note: Make sure that the pump processes transfer all the changes to the target server. The Lag at the Chkpt and Time Since Chkpt should be 0. This can be confirmed by using the info all command after connecting to the ggsci prompt.

  4. Upgrade the source application.

  5. After a successful upgrade, do not release the source applications to end users. Ensure that you stop the source applications but keep the source databases up and accessible.

  6. Ensure Incremental Changes (DDL and DML changes during the upgrade) are synced. Make sure the data in the source is in sync with the replication tables. The Lag for Chkpt and Time Since Chkpt in both the source and target databases should be 0.

  7. Stop all Golden Gate Processes (EXTRACTS, REPLICATS, PMSRVR, JAGENT, MANAGER) in the source and the target.

  8. Download and apply Golden Gate patch 35580180 (for Solaris and Linux) or 35682480 (for AIX) and Oracle GoldenGate Monitor Agent patch 34362913 on Source Side.

    Note: Do not start any GoldenGate processes after applying the patch.

  9. Bring up the source application.

Back to Top

Upgrade OUAW without Upgrading Source Applications

Note: This section refers to the sources that you are not required to upgrade. It is valid only for sources that are compatible with both Oracle Utilities Analytics Warehouse 2.7.0.2.1 and 2.8.0.2.0.

  1. Ensure the source application, source database, and target database are up and running.

  2. Make sure the data in the source is synchronized with the replication tables. The Lag for Chkpt and Time Since Chkpt in both the source and target databases should be 0.

  3. Stop all Golden Gate Processes (EXTRACTS, REPLICATS, PMSRVR, JAGENT, MANAGER) in the source and the target.

  4. Download and apply Golden Gate patch 35580180 (for Solaris and Linux) or 35682480 (for AIX) and Oracle GoldenGate Monitor Agent patch 34362913 on Source Side.

    Note: Do not start any GoldenGate processes after applying the patch.

Back to Top