3 Cloning Cloud EPM Environments

The Clone Environment feature provides a screen-based way to clone a business process environment including Narrative Reporting.

You can clone the following types of records:

  • User and Application Roles (Identity domain artifacts)
  • Data Management (Optional) - For Account Reconciliation, Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, Profitability and Cost Management, and Tax Reporting
  • Application Audit (Optional) - For Enterprise Profitability and Cost Management, FreeForm, and Planning
  • Job Console (Optional) -For Enterprise Profitability and Cost Management, Financial Consolidation and Close, FreeForm, Planning, and Tax Reporting
  • Stored Snapshot and Files (Content of the inbox, outbox, and stored snapshots)
  • Daily Maintenance Start Time
  • Application Properties (Optional) - For Account Reconciliation only

Note:

  • You use the Clone Environment screen to clone using the latest maintenance snapshot only.
  • You can use the cloneEnvironment EPM Automate command, which provides an alternative to using the Clone Environment screen. Using this command allows you to clone environments using an Environment Backup or an older maintenance snapshot.

Supported Cloning Scenarios

Cloning of environment is particularly useful in migration scenarios, such as:

  • Cloning from primary environment to standby environment for Disaster Recovery
  • Cloning from production to test environments
  • Cloning from test to production environments

Unsupported Cloning Scenarios

  • See Version Compatibility in the Getting Started Guide for Administrators to understand unsupported cloning scenarios.
  • Cloning may fail if Planning contains a renamed seeded period member that has been replaced by a custom period member. For example, renaming the seeded YearTotal period member to unused_YearTotal and adding an alternate type period member with the original seeded name (for example, YearTotal) can cause cloning to fail.

Which Snapshot Can be Cloned?

This cloning process uses the current snapshot, called Artifact Snapshot, created during the last daily maintenance.

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

Attempting to clone an environment that is currently generating or archiving the snapshot, such as during daily maintenance, will result in a File not found error.

Troubleshooting

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