1. Administering Migration for Oracle Enterprise Performance Management Cloud
  2. Cloning EPM Cloud Environments

3 Cloning EPM Cloud Environments

The Clone Environment feature is a screen-based way to clone an environment (including Narrative Reporting environments) and, optionally, identity domain artifacts (users and predefined role assignments), and contents of the inbox, outbox, and stored snapshots.

Additionally, for Account Reconciliation, Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Profitability and Cost Management, Enterprise Profitability and Cost Management, Tax Reporting, Sales Planning, and Strategic Workforce Planning you can clone Data Management records.

You can also clone the Job Console records available in Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Enterprise Profitability and Cost Management, and Tax Reporting environments, and the application audit data available in Planning, Planning Modules, FreeForm, and Enterprise Profitability and Cost Management environments.

This command is an alternative to using the cloneEnvironment EPM Automate command.

Supported Cloning Scenarios

Cloning of environment is useful in migration scenarios, including the following:

  • Migrating from Oracle Cloud Classic to OCI (Gen 2) Oracle Enterprise Performance Management Cloud
  • Production to test cloning
  • Test to production cloning

Unsupported Cloning Scenarios

Account Reconciliation, Oracle Enterprise Data Management Cloud, and Narrative Reporting do not support the cloning of an environment to an environment that is on a previous monthly update.

Cloning may fail if Planning contains a renamed seeded period member that has been supplanted by a custom period member. For example, you renamed the seeded YearTotal Period member to unused_YearTotal and then added an alternate type period member with the original seeded member name (YearTotal in this example).

Which Snapshot Can be Cloned?

This feature uses the current snapshot, named Artifact Snapshot, created by the last daily maintenance.

If changes you made to the environment after the last daily maintenance must be present in the snapshot being cloned, run the runDailyMaintenance EPM Automate command to regenerate Artifact Snapshot.

Note:

If you attempt to clone an environment that is in the process of generating or archiving the current snapshot; for example, during the daily maintenance, you will receive the File not found error.

Important Considerations

When you clone an environment, EPM Cloud automatically completes all the actions required to create an exact copy of the current application in a target environment. Prepare the target environment before initiating this process:

  • Create and archive the latest backup snapshot of the target environment.

    Cloning does not delete the existing snapshots, or the files in the inbox and outbox of the target environment. If Artifact Snapshot exists in the target environment, cloning renames it as Artifact Snapshot_DATE_TIME; for example, Artifact Snapshot_2021_04_30_17:06:06.

  • Initiate cloning after the scheduled daily maintenance of the source and target environments. If the daily maintenance of the source environment starts while cloning is going on, the cloning process will be terminated. The cloning process on the target environment is not affected even if the cloning is going on at the start time of the daily maintenance. In this scenario, the daily maintenance will run after the cloning is complete.

    If the cloning of your environment takes a long time, reschedule the daily maintenance start time on the source environment to avoid the cloning process from being terminated. For information on resetting the daily maintenance start time, see:

About Account Reconciliation Application Settings

After cloning, the target Account Reconciliation application settings will reset to their default values. If you wish to retain the target application settings, export them from the source environment using the exportARApplicationProperties EPM Automate command. Then, after the cloning is complete, import the application properties into the target environment using the importARApplicationProperties EPM Automate command.

Handling Essbase Version During Cloning

If there is a mismatch between the Oracle Essbase version in the source and target environment, the cloning process will upgrade the Essbase version in the target environment to match that of the source environment. However, it will not downgrade the Essbase version in the target environment to match that of the source. For example, if the source is an EPM Enterprise Cloud Service environment with Hybrid-enabled Essbase and the target is a legacy EPM Cloud environment with Non-Hybrid Essbase, the clone process will upgrade the target environment to use Hybrid-enabled Essbase.

If you are cloning legacy environments, the cloning process handles the Essbase version as discussed in the following scenarios:

  • Scenario 1 - You are cloning a source legacy environment that uses an Essbase version that does not support Hybrid cubes to a target legacy environment that uses an Essbase version that supports Hybrid cubes. In this scenario, the Essbase in the target environment is downgraded to match the version in the source environment.
  • Scenario 2: You are cloning a source legacy environment that uses an Essbase version that supports Hybrid cubes to a target legacy environment that uses an Essbase version that does not support Hybrid cubes. In this scenario, the Essbase in the target environment is upgraded to match the version in the source environment.
  • Scenario 3: You are cloning a source legacy environment that uses an Essbase version that does not support Hybrid cubes to a target EPM Standard Cloud Service or EPM Enterprise Cloud Service environment, which, by default, uses an Essbase version that supports Hybrid cubes. In this scenario, the Essbase in the target environment is not downgraded to match the version in the source environment.

See Migration Paths for EPM Standard Cloud Service and EPM Enterprise Cloud Service Snapshots in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.

Troubleshooting

See Resolving Clone Environment Issues in Oracle Enterprise Performance Management Cloud Operations Guide.