A while back (nearly 2 years ago), I wrote about the Clone Environment feature. Oracle has continued to improve this feature and it seemed like a good time to update that original post. Note: I am detailing the process for EPM Planning. Some features may or may not be available for other EPM products.
Some things about it are still the same. It is a full migration of the application using the most recent Artifact Snapshot. You can update this snapshot by running the EPM Automate command runDailyMaintenance. The target environment is still recreated as part of the process. You can use other methods like copySnapshotFromInstance if you need flexibility in choosing a source snapshot.
The newer features include more choices in what gets cloned. In the early versions of Clone Environment, the only option available was Users and Predefined Roles.
Now there are multiple options available in what to migrate.
- Select Users and Predefined Roles to clone users and their predefined role assignments.
- Select Data Management to clone data management records. This may take a long time to process depending on how much data is in the staging tables in the source application. Also, per Oracle documentation, “Clone Data Management records only if both the source and target environments are on the same monthly update, or the target environment is one update newer than the source environment. For example, you can clone 22.01 Data Management records to another 22.01 environment or to a 22.02 environment only.”
- Select Application Audit to clone audit records.
- Select Job Console to clone the job records.
- Select Stored Snapshots and Files to clone the files in the inbox and outbox, and the stored snapshots. This could take a long time depending on how many files and snapshots are in the source application.
- Select Daily Maintenance Start Time to clone the current maintenance start time of the source application.
That’s a lot more options than when this was first introduced. When I am cloning from Prod to Test, I normally check Data Management and Daily Maintenance Start Time and leave the other options unchecked. It really depends on the purpose of the clone.
When the clone completes, some settings and configurations may need to be updated. Make sure the application is open to all users or restricted to administrators as needed.
Update any connections to other applications.
There are some other post-Clone items to consider, refer to full Oracle documentation for more information.
As always, happy EPM’ng!
2 thoughts on “EPM Cloud Planning Clone Environment”
Hi Paul. Have you also tried using EPM Automate to clone environments? I ask because I can’t seem to get it to work. My daily maintenance process renames the artifact snapshot every night and for some reason I don’t seem to be able to use such a renamed artifact snapshot in the epm automate cloneEnvironment command (our snapshots are renamed as follows: AS_TEST_YYYYMMDD). Surprisingly, the UI clone environment process identifies and clones the snapshot without any problems.
I have used EPM Automate, I posted about it a while ago. The commands should be the same, I don’t think much would have changed. https://randomepmnotes.com/2019/06/08/epm-automate-using-copysnapshotfrominstance-to-migrate/