Steps to Clone Environments

While cloning an environment, you have these options depending on the predefined role of the user account specified for the target environment:

Table 3-1 Available Clone Environment Options

Predefined Role in the Target Environment Available Clone Options
Service Administrator Clone the application artifacts. Optionally clone Data Management records, audit data, Job Console records, contents of the inbox and outbox, and stored snapshots. Cannot clone users and predefined role assignments.
Service Administrator and Identity Domain Administrator Clone the application artifacts. Optionally clone users and their predefined role assignments, Data Management records, audit data, Job Console records, contents of the inbox and outbox, and stored snapshots.

To clone an environment:

  1. Sign in to the environment that you want to clone. You should sign in as a Service Administrator or as a Service Administrator, who also has the Identity Domain Administrator predefined role.

    For Oracle Cloud Classic to OCI cloning, you must sign in as a Service Administrator, who also has the Identity Domain Administrator predefined role to ensure that users and their roles are cloned to the OCI environment.

  2. Complete a step:

    Click Tools, and then Clone Environment.

    Profitability and Cost Management only: Click Application, and then Clone Environment.
    Clone Environment screen

  3. In Target URL, enter the URL of the environment that will become the cloned environment; for example, https://testExample-idDomain.pbcs.us1.oraclecloud.com.
  4. In Username, enter the user name of a Service Administrator who may also have the Identity Domain Administrator predefined role.

    For Oracle Cloud Classic to OCI cloning, you must enter the user name of a user who has Service Administrator and Identity Domain Administrator predefined roles in the target environment.

    This user must be able to log into the target environment using identity domain credentials.

  5. In Password, enter the identity domain password of the user specified in Username.
  6. Optional: Select the Users and Predefined Roles check box to clone users and their predefined role assignments.

    If you are performing an Oracle Cloud Classic to OCI migration, you must select this check box.

    • Changes to the predefined roles of the user will be updated based on the roles assigned in the source snapshot. However, role assignments in the target will not be removed to match those in the source snapshot. For example, assume that jdoe is assigned to the Power User predefined role in the target environment, but has only the User role in the source snapshot. In this situation, this command assigns jdoe to the User role and does not remove the Power User role assignment in the target environment.
    • This option does not delete existing users from the target environment if they don't exist in the source snapshot. For example, jdoe has an account in the target environment, but this account is not present in the source snapshot. In this situation, the account of jdoe in the target environment is not deleted.
    • This option adds users that do not exist in the target environment; it does not update current user properties in the target environment even if those are different in the source snapshot. For example, if the last name of jdoe in the source snapshot is spelled differently in the target environment, the change will not be made in the target environment.
    • This command does not change existing users' passwords in the target environment even if it is different in the source snapshot.

      A random password is assigned to new users in the target environment. New users will receive account activation emails prompting them to change passwords.

  7. Optional: for environments other than Oracle Enterprise Data Management Cloud and Narrative Reporting only: Deselect the Data Management check box if you do not want to clone Data Management records. Cloning of Data Management records may take a long time if the staging tables contain a very large number of records.

    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.

  8. Optional: for Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Tax Reporting, and Enterprise Profitability and Cost Management only: Deselect the Job Console check box if you do not want to clone Job Console records.
  9. Optional: for Planning, Planning Modules, FreeForm, and Enterprise Profitability and Cost Management only: Deselect the Application Audit check box if you do not want to clone application audit records.

    Note:

    Application audit data of Financial Consolidation and Close, and Tax Reporting is, by default, included in the snapshot.
  10. Optional: Select the Stored Snapshots and Files check box if you want to clone the contents of inbox and outbox, and stored snapshots. This process may take a long time depending on the number and size of stored snapshots and files in inbox and outbox.
  11. Optional: Deselect the DailyMaintenanceStartTime check box to keep the current maintenance start time of the target environment. Otherwise, the maintainence start time will be reset to that of the source environment from which the snapshot was cloned.
  12. Click Clone to initiate the process.