1. Oracle Enterprise Performance Management Cloud Operations Guide
  2. Making EPM Cloud-Related Requests
  3. EPM Cloud Classic to Oracle Cloud Infrastructure (OCI) Migration
  4. Oracle-Managed Migration

Oracle-Managed Migration

Oracle will migrate all Classic UK Government Oracle Enterprise Performance Management Cloud environments to OCI in Wave 9. Oracle will migrate your Classic environments in a seamless manner on a predefined schedule. Oracle will send a notification to the Service Administrators of these environments with the following information:

  • A list of the Service URLs of the current Classic environments.
  • Domain names of the new environments in OCI (in most cases, the current domain names are used).
  • Location of OCI data centers where the environments will be created.
  • The default Domain Administrator and Service Administrator email addresses on record with Oracle. These will be used as the Domain Administrator and Service Administrator for the new OCI environments.

This notification, sent in the beginning of April 2024, specifies that OCI environments will be available in May 2024. You can request Oracle to change the Domain Administrator and Service Administrator emails by creating a service request containing the updated information by the date provided in the notification. You cannot change the new domain name or the OCI data center location.

In May 2024, Oracle provides OCI environments equaling the current number of Classic environments. These OCI environments use the domain names and OCI data centers provided earlier and do not have any application or users on them. The default Domain Administrator and Service Administrator specified in the notification email get the Activate Your Account email.

Note:

Because your OCI environments may be provisioned at different times, you may not receive notification emails for all the environments at the same time.

When you receive the OCI environments, complete these optional activities before July 2024.

  • Configure Single Sign On (SSO) with your Identity Provider if you utilize SSO in your Classic environments
  • Configure IP Allowlists for the OCI Environments if you use allowlists with your Classic environments
  • If you want to perform tests in OCI environments:

    Note:

    You need not clone and test every Classic environment. For example, if you have the same application on a test and production environment, test it only in one of the environments. Additionally, it is not necessary to clone environments that you do not plan to test.
    • Clone the applications from Classic environments to the corresponding OCI environments using these information sources:
    • Complete any test you want to run. Testing is optional. During this testing period, production updates and changes must be performed on the Classic environments.

      Note:

      If you attempt to create a service request at this stage, Oracle Support shows only the OCI accounts and environments corresponding to the Classic accounts and environments that are in the process of being migrated. In this scenario, to create a service request for a Classic environment that is in the process of being migrated:
      • Select an OCI environment in Oracle Support
      • In service request Summary and Description, specify the service URL of the Classic environment for which you are creating the service request.
      • Include the Provide Feedback reference number from the Classic environment.

In July 2024, while applying the monthly update 24.07 during the daily maintenance window, Oracle automatically clones your OCI environments from Classic environments (this will override any test applications you already have on the OCI environments), change the DNS configuration so that the existing Classic service URLs are routed to the OCI environments, and terminate Classic environments. Cloning of test environments is done on the first Friday of July 2024. Cloning of production environments takes place on the third Friday of July 2024.

Daily Maintenance on the Data Migration Day

The daily maintenance duration on the day of the data migration will be much longer than the duration of daily maintenance on other days. Use the following general guidelines to plan for the daily maintenance on the day of the data migration

  • If the total data size on the Classic environment is 100 GB or less, the daily maintenance will take up to six hours.
  • If the total data size on the Classic environment is more than 100 GB, the daily maintenance will take up to 12 hours.
The total data size in the environment is identified in the Activity Report of the Classic environment as Customer Data on Disk in GB in the Application Size table. The total data size is also displayed in the My Services portal as the value of the Size of Data (GB) metric.

Note:

  1. The migration from Classic to OCI environment will occur on the scheduled date even if you have requested to skip the 24.07 update (using the skipUpdate EPM Automate command or by raising a service request). In this scenario, the OCI environment will have the same monthly update as the corresponding Classic environment, and skip update for 24.07 will be active on the OCI environment.
  2. If your Classic environment is on a one-off patch not to be merged back in 24.07, the migration from Classic to OCI environment will still occur on the scheduled date. In this scenario, the OCI environment will have the same one-off patch as the corresponding Classic environment.
  3. If you requested Oracle to apply the monthly update 24.07 on your Classic production environment before the third Friday of July 2024, the migration will occur during the daily maintenance when your Classic production environment is updated with the monthly update (before third Friday of July 2024) .
  4. If your Classic environment is going through a scheduled or unscheduled maintenance at the time of the daily maintenance when your migration is scheduled, since the scheduled daily maintenance is skipped, the migration will occur during the daily maintenance on the next day.

This migration is seamless; Oracle migrates your application data, users, custom governor limits, and other artifacts to the new OCI environments. From this point, the OCI URLs that you've been using for testing do not work, Instead, current URLs of Classic environments are routed to the OCI environments. However, you still use new URLs to access the My Services portal.

Important Considerations

  • Users migrated from Classic to OCI environments will receive password reset emails prompting them to sign into OCI environments. This is the same Activate Your Account email indicated previously. If Classic passwords are compliant with the Identity Cloud Services password policy, which can be customized by an Identity Domain Administrator, users can set their OCI passwords to be the same as their Classic passwords.

    If users with Service Administrator predefined role change their OCI passwords, update the passwords used in areas including the following:

    • EPM Automate scripts
    • REST API-based scripts
    • EPM Agent configuration
    • Navigation Flow configuration. To update Navigation Flows, complete tasks using these resources:
      • "Editing a Navigation Flow" in the Administration guide of your business process to use the Navigation Flows screens
      • Update a Connection in REST API for Oracle Enterprise Performance Management Cloud
  • The Identity Domain Administrator role assignment is not cloned. Users with only the Identity Domain Administrator role assignment are not cloned to the OCI environment.

    Users assigned to a combination of Identity Domain Administrator role and predefined roles in the Classic environment are cloned, but assigned only to the respective predefined roles in the OCI environment. These users will not have the Identity Domain Administrator role in the OCI environment.

  • The OCI environments are always created in the primordial stripe of Identity Cloud Services. However, if your production and test Classic environments are not in the same identity domain because you had relocated one of them to a different domain, your production OCI environment is created in the primordial stripe while the test environment is created in the secondary stripe of the same domain. You still can manage them separately as before. Also, because of DNS configuration change, the URLs of the production and test environments will stay the same as they were for Classic environments.

  • The domain names of the existing Classic environments are preserved unless they contain characters not supported by OCI. In OCI, domain names must:

    • Contain only lower-case English letters and numbers
    • Start with a letter
    • Not exceed 32 characters

    If the Classic domain name contains a hyphen, it is updated to remove the hyphen. For example, the Classic domain name acme-test, is changed to acmetest. However, the domain name in the URL remains the same.

  • After the migration is complete, Oracle changes the DNS configuration to route traffic to the Classic environment URLs to the corresponding OCI environments. If these OCI environments are deleted for any reason (for example, to change the service name or to move to a different data center), the routing of Classic URLs will fail because the DNS configuration will continue to route to the original OCI environments that were deleted.

    Because the newly recreated environments will use different URLs than those of the migrated OCI environments, you must update the URLs used in EPM Automate and REST API scripts, Navigation Flow configurations, bookmarks, shared and private connections in Oracle Smart View for Office, and so on, with the new OCI URLs as needed. You must also announce the new URLs to all users who need to access the recreated environments.

  • If you are using IP address of the source EPM Cloud environment anywhere (for example, in proxy configuration as an allowed outgoing IP address), find the new IP address of the environment using nslookup or ping after the migration and update the configuration with the new IP address.

    Similarly, if you have added the outbound IP address of the Classic data center in the allow list of any other environment (for example, in a Fusion ERP environment), change it to the outbound IP address of the new OCI region. See Outbound IP Addresses of EPM Cloud Data Centers and Regions to identify the outbound IP address of the OCI region of your environment.

  • If you use EPM Agent to communicate with EPM Cloud, ensure that you are using EPM Agent version 22.07 or higher. If the EPM Agent is older than version 22.07, you may get a certificate error while connecting to EPM Cloud after the OCI data migration is complete.