Importing Artifacts and Application from a Snapshot

You can import snapshots to create a clone of another environment or to migrate artifacts from another environment. Before you can initiate such process, you must upload the backup or incremental snapshot that you want to import into the target environment.

Do not run jobs in an environment while an import operation is in progress. Because the underlying data and metadata may be affected by an import operation, jobs may result in inaccurate results.

Methods to Upload Snapshots and Files

• Use Migration to download the snapshot from the source environment and then upload it to the target environment. See Downloading Files and Snapshots from an Environment and Uploading Archives to the Service .
• Use the downloadFile and uploadFile EPM Automate commands.
• Use the copySnapshotFromInstance EPM Automate command to copy a snapshot from another environment.

Key Considerations

• Excepting Strategic Modeling and Account Reconciliation, Oracle Enterprise Performance Management Cloud supports snapshot compatibility for one monthly cycle only; you can migrate maintenance snapshots from the test environment to the production environment and vice versa.

  Strategic Modeling and Account Reconciliation snapshots are not backward compatible. Account Reconciliation supports the migration of individual artifacts to a previous monthly update, except for the Application Snapshot artifact.

  The import process displays the following warning if the snapshot used for the process is not compatible with the current version of the environment.

  EPMLCM-26000: This snapshot is from EPM Cloud VERSION_NUMBER that is incompatible with this update and may result in import errors.

  You can upgrade incompatible snapshots other than Account Reconciliation and Oracle Enterprise Data Management Cloud snapshots to make them compatible with the current version of an environment. See "Recreating an Old EPM Cloud Environment for Audits" in Working with EPM Automate for Oracle Enterprise Performance Management Cloud.

• Only use LCM to import Journals if no Journals exist in the application. Otherwise, existing Journals will be deleted.

• After performing an LCM import, it’s recommended to sign off and sign back in after the LCM import completes.

• After you initiate an import operation, EPM Cloud displays the Migration Status Report. Click Refresh periodically to update the report and monitor progress.

  If an import fails for any reason, the Migration Status Report displays Failed as the status. Click the status to open the Migration Details screen, which indicates why the import failed and the corrective action to take.

• Migration does not support the import of application audit records.

• If you are not importing users and a user in the source snapshot does not have a predefined role on the target environment, the following error is displayed:

  EPMIE-00070: Failed to find user during assigned roles import.

• For Data Management: The import process may take longer if the snapshot contains staging data.

• For Oracle Enterprise Data Management Cloud: The system is placed in migration mode when you import artifacts and snapshots.

Troubleshooting

See Resolving Import and Export and Backup Errors in Oracle Enterprise Performance Management Cloud Operations Guide.

Importing a Backup to Create a Clone of Another Environment

You import a backup snapshot (by default, named Backup Date) to create a clone of another environment.

Don't attempt to import a backup snapshot into an environment where an application already exists. If you want to import a backup snapshot into an environment with an existing application, first run the recreate EPM Automate command to restore your environment to a clean state, and then import the backup snapshot.

To import a backup to create a clone of another environment:

1. Access Migration. See Accessing Migration for Lifecycle Management.

2. Click Snapshots.

3. Click (Actions) next to the backup snapshot that you want to import, and then select Import.

4. In Import, click OK.

   The Migration Status Report, which helps you monitor the import progress opens. Refresh the report frequently to verify that the operation completes without errors.

Importing Artifacts into an Environment

You import specific artifacts from a backup snapshot or an incremental snapshot to migrate artifacts from one environment to another. For example, you can import a snapshot of tested artifacts from a test environment into a production environment. Similarly, you can import Essbase data and artifacts from an incremental snapshot created by exporting them from another environment.

The import of some artifacts is governed by the import settings specified for the environment. See Setting Import Options.

To import artifacts:

1. Access Migration. See Accessing Migration for Lifecycle Management.
2. Click Snapshots.
3. Expand the snapshot containing the artifacts that you want to import.
4. Select artifacts to import.

   • To import all artifacts of a specific component:

     1. Expand the snapshot, and then click a component name; for example HP–Vision, to access a list of artifacts of the Vision sample application included in the snapshot.

     2. Click Select All.

     3. Click Import.

   • To import specific artifacts of a component:

     1. Expand the snapshot, and then click a component name; for example HP–Vision to access a list of artifacts of the Vision sample application included in the snapshot.

     2. In Artifact List, expand the list of available artifacts and then select the artifacts that you want to import.

     3. Optional: Click (Selected Artifacts), and then verify the list of artifacts selected for import.
     4. Click Import.
5. Click OK to confirm that you want to initiate the import operation.
   The Migration Status Report opens. Use this report to monitor the progress of the operation.