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 Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Account Reconciliation, Profitability and Cost Management, Enterprise Profitability and Cost Management, Tax Reporting, Oracle Sales Planning Cloud, and Oracle Strategic Workforce Planning Cloud 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
Note: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.
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
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.
Handling Essbase Version During Cloning
If there is a mismatch between the 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 the source is a legacy EPM Cloud environment with Non-Hybrid Essbase and the target is an EPM Enterprise Cloud Service environment with Hybrid-enabled Essbase, the clone process will not downgrade the target environment to use Non-hybrid Essbase. Because of this incompatibility, the snapshot import from source to target environment fails in some scenarios. For a list of supported migration paths, 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 .
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. You need to prepare the target environment before initiating this process, which takes some time to complete. Some considerations include the following:
- Creating and archiving the latest backup snapshot of the target environment. The cloning process does not delete existing snapshots or the files in the inbox and outbox of the target environment.
Artifact Snapshotexists in the target environment, the clone process renames it as
Artifact Snapshot_DATE_TIME; for example,
- Initiate the cloning process after the scheduled daily maintenance of the source and target environments. Be sure to allow sufficient time for the process to complete.