Migration of EURA Environments to EU Sovereign Cloud (OC19)

Oracle will migrate all Oracle Fusion Cloud Enterprise Performance Management and Oracle Fusion Cloud Enterprise Data Management environments in the EURA regions in OC1 realm to the OC19 (EU Sovereign Cloud) realm on a predefined schedule. Oracle will notify the Service Administrators of these environments and provide them with a list of the current EURA service URLs. The notification will also provide information on the steps that must be completed and the deadlines for completing them.

The migration process will be as follows:

1. On the date specified in the initial notification, Oracle will send a subscription notification email to Service Administrators. See The Subscription Activation Email in the Getting Started Guide for Administrators.

2. After receiving the subscription notification, create a new Oracle Cloud account or add the subscription to an existing account. See these topics in the Getting Started Guide for Administrators:

   • Creating a New Cloud Account
   • Adding Subscription to an Existing Cloud Account

   If you create a new cloud account:

   • You can choose a home region from among these OC19 regions:
     • EU Sovereign Central (Frankfurt) - eu-frankfurt-2
     • EU Sovereign South (Madrid) - eu-madrid-2
   • Create a new cloud account name or use the name of the cloud account you currently have in the EURA regions.

3. After completing the preceding step, create a technical service request to inform Oracle that the Oracle Cloud account creation is complete.

4. On receiving the technical service request, Oracle will enable processing so that you can start creating your environments. For instructions, see Creating an Environment in the Getting Started Guide for Administrators.

   Create as many OC19 environments as the number of your EURA environments. The deadline for creating environments will be specified in the initial notification.

5. After creating your OC19 environments, complete these optional activities before the date specified in the initial notification.

   • Configure Single Sign On (SSO) with your Identity Provider if you utilize SSO in your EURA environments and you created OC19 environments in a new IAM domain where SSO is not already setup.
   • Set up network perimeter if you use allowlists with your EURA environments. See:
     • Manage Oracle Identity Cloud Service Network Perimeters in Administering Oracle Identity Cloud Service.
     • Setting up Network Perimeter in the Getting Started Guide for Administrators

6. Update the technical service request that you created previously (in step 3) with a mapping of the service URLs of the current EURA environments to those of the newly created OC19 environments.

7. On the dates specified in the initial notification, Oracle will clone the EURA test and production environments to OC19 environments and change the DNS configuration so that the existing EURA service URLs are routed to the OC19 environments.

   Cloning of the test and production environments will occur on different dates as specified in the initial notification. Oracle will terminate your EURA environments soon after the cloning of the production environments is complete.

Duration of Data Migration

The duration of the data migration to OC19 will depend on the data size on the EURA environments. Use the following general guidelines to plan for the data migration duration:

• If the total data size on the EURA environment is 100 GB or less, the data migration will take up to six hours.
• If the total data size on the EURA environment is more than 100 GB, the data migration will take up to 12 hours.

The total data size in the environment is identified in the Activity Report of the EURA environment as Customer Data on Disk in GB in the Application Size table.

The data migration is seamless; Oracle will migrate your application data, users, custom governor limits, and other artifacts to the new OC19 environments. From this point, the original OC19 URLs will not work, Instead, the URLs of EURA environments will be routed to the OC19 environments. However, your Cloud Console URL will change.

Important Considerations

• Users of environments that are migrated from EURA to OC19 will receive password reset (Activate Your Account) emails prompting them to sign into the OC19 environments. Users can set their OC19 passwords to be the same as their EURA passwords.

  If users with Service Administrator predefined role change their OC19 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 the REST APIs for Oracle Fusion Cloud EPM guide
• The Identity Domain Administrator role assignment is not cloned. Users with only the Identity Domain Administrator role assignment are not cloned to the OC19 environment.

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

• After the migration is complete, Oracle changes the DNS configuration to route traffic to the EURA environment URLs to the corresponding OC19 environments.

  Note:

  If these OC19 environments are deleted in the future for any reason (for example, to change the service name or to move to a different region), the routing of EURA URLs will fail because the DNS configuration will continue to route to the original OC19 environments that were deleted. Any newly created OC19 environments will have different URLs than those of the migrated OC19 environments. In such cases, 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 OC19 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 Cloud EPM 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 it is created and update the configuration with the new IP address.

  Similarly, if you have added the outbound IP address of the EURA region 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 OC19 region. See Outbound IP Addresses of Cloud EPM Regions to identify the outbound IP address of the OC19 region of your environment.

• If you previously added the domains epm.eu-frankfurt-1.ocs.oraclecloud.com and epm.eu-amsterdam-1.ocs.oraclecloud.com in the allowlist of the firewall, you must also add the new OC19 canonical names to the allowlist. To identify the canonical names, use nslookup.

  For example, if the EURA environment URL is https://epm2-mydomain.epm.eu-frankfurt-1.ocs.oraclecloud.com/, running an nslook for epm2-mydomain.epm.eu-frankfurt-1.ocs.oraclecloud.com will return the canonical name epm2-mydomain.epm.eu-frankfurt-1.ocs.oraclecloud.eu. Add the domain (epm.eu-frankfurt-1.ocs.oraclecloud.eu) from the canonical name to the firewall's allowlist.

  To ensure that all necessary canonical names are covered, add these domains to the firewall's allowlist:

  • epm.eu-frankfurt-2.ocs.oraclecloud.eu
  • epm.eu-madrid-2.ocs.oraclecloud.eu