Brovanture OCI Migration

Oracle Cloud Infrastructure (OCI) Gen2 Migration for Oracle Cloud EPM

Tej Bhople
Brovanture Consultant

2023 is the year of Oracle Cloud Infrastructure (OCI) Gen2 migration emails from Oracle. Over time, and by end of 2023, Oracle plans to migrate all Oracle Cloud EPM instances in Classic commercial data centres to OCI. Thus, the emails to inform customers of the change to their Oracle Cloud EPM environment.

This will affect all Oracle Cloud EPM instances including new orders of EPM Standard Cloud Service and EPM Enterprise Cloud Service and customers with older Oracle EPM Cloud Services subscriptions. Today around 26% of Oracle Cloud EPM environments including new and migrated ones are already on OCI.

Oracle’s data centres around the globe are standardizing on the OCI architecture which delivers greater performance and reliability. There are a number of great features in Oracle Cloud EPM that are available only in OCI.

There are two possible options for migration to OCI.

  • Oracle Managed Migration
  • Customer Managed Migration

1.     Oracle Managed Migration

Steps for Oracle Managed Migration

  • Oracle will notify customer Service Administrators when the OCI migration will occur for their Classic environments – at least 1 month before the scheduled migration date.
  • On the scheduled migration date, Oracle provides new OCI environments equalling the current number of Classic environments.
    • OCI environments will have new service URLs. (with same domain name like classic cloud URLs)
    • Classic environments continue to work at the same time.
  • The customer has 2 months to finish testing.
  • At the end of the 2 months, Oracle will migrate the application and all artifacts from Classic Cloud to OCI Cloud (TEST environment on the first Friday and PROD environment on the third Friday of month)

2.     Customer Managed Migration

Steps for Customer Managed Migration

  • Customer creates a Service Request (SR) for their OCI migration.
  • Flexibility to choose domain name, data centre within the CSV file in the SR
  • Oracle provides new OCI environments equalling the current number of Classic environments.
  • Customer has 6 months to finish testing.
  • Classic environments continue to work during these 6 months.
  • Oracle will terminate the Classic environments after 6 months.
  • Customer can request termination of Classic environments via SR if their migration is finished before that.

Post migration steps (Customer Managed migration)

  • Service Administrator Tasks
    • Announce URLs of OCI environments to All Oracle Cloud EPM users.
    • Modify scripts to change URLs.
    • If Navigation Flows are used, update Connections to change URLs (and possibly passwords).
    • If Oracle EPM Agent is used, update its configuration to change URLs (and possibly passwords).
    • If there are any other integrations, such as, with FDMEE or NetSuite, update them to change URLs (and possibly passwords).
  • Individual User Tasks
    • Update Oracle Smart View shared and private connections to change URLs.
    • Modify bookmarks to point to the new URLs.

The biggest advantage with customer managed migration is flexibility to perform testing over a period of 6 months and choosing the logical domain name.

E.g. Instead of “a123456”, domain name can be “customername1”

Steps to migrate applications and artifacts (Irrespective of ownership)

  • If Single Sign On (SSO) was setup in My Services for Classic environments, re-configure it for IDCS for OCI environments.
  • If IP allowlists were configured in My Services for Classic environments, use EPM Automate command setIPAllowList to re-configure them for the new OCI environments.
  • Clone ONLY the application from each Classic environment to corresponding OCI environment using Clone Environment – the schedule and order is customer defined.
  • Complete the testing for all applications in 6 months.
  • After successful testing, clone all artifacts (application, users and their roles, data management records, audit history, job console history, and stored snapshots and files) from the Classic environments to corresponding OCI environments – the schedule and order is customer defined.

Brovanture has considerable experience helping our clients to successfully execute both of these approaches. Please feel free to contact us when you are receive an Oracle Cloud EPM OCI migration email from Oracle. We are very happy to discuss this with you and give you a demo of how we have approached this.

Until next time


For more blogs from Tej –