Resolving Clone Environment Issues

Applies to

Oracle Hyperion Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Tax Reporting, Account Reconciliation, Oracle Hyperion Profitability and Cost Management, Enterprise Profitability and Cost Management, Oracle Enterprise Data Management Cloud, Narrative Reporting, Sales Planning, and Strategic Workforce Planning.

The Clone Environment feature of Oracle Hyperion Enterprise Performance Management System Lifecycle Management is a screen-based way to clone an environment and, optionally, identity domain artifacts (users and roles). The cloneEnvironment EPM Automate command provides equivalent function. These options provide alternatives to writing an EPM Automate script to clone environments.

If you encounter an error while using the Clone Environment feature, troubleshoot it using these steps:

• Review the important considerations available in Cloning EPM Cloud Environments in Oracle Enterprise Performance Management System Lifecycle Management Guide.
• If the error indicates that the migration has failed, refer to Migration Paths for EPM Standard Cloud Service and EPM Enterprise Cloud Service Snapshots in Oracle Enterprise Performance Management Cloud Getting Started with Oracle Enterprise Performance Management Cloud for Administrators to check whether the source and target environments are compatible for migration.

Considerations for IP Allowlist-Enabled Environments

If the source or destination environment has IP allowlist enabled, see Outbound IP Addresses of EPM Cloud Data Centers and Regions to verify that the allowlist in the destination environment contains the required IP address of the source environment, and that the allowlist in the source environment contains the required IP address of the destination environment.

Getting Help

If the issue is only with the Clone Environment screen, use EPM Automate to clone the environment until the issue is resolved. If you cannot resolve the issue, get help from Oracle:

• Create Provide Feedback submissions for both source and target environments. Optionally, authorize Oracle to access the maintenance snapshots of the environments by consenting to application snapshot submission. See Creating a Provide Feedback Submission.
• Submit a technical service request that identifies both the Provide Feedback reference numbers. See Submitting a Technical Service Request. The service request must contain:
  • A screenshot of the error message.
  • Whether you chose to clone users and roles.
  • Did this issue start after the latest monthly update?
  • Whether this is a critical outage.