About Exports and Imports

About Exports

The Migration Status Report, which is displayed after you initiate the export operation from Oracle Hyperion Enterprise Performance Management System Lifecycle Management, indicates Failed as the status if the operation fails for any reason. Click Failed in the report to open the Migration Details screen, which indicates why the export failed and the corrective action. In most cases, you can fix the export or backup errors yourself by reviewing the Migration Status Report. You can attempt the export operation again after correcting the error that caused the export to fail.

About Imports

You import snapshots to create a clone of another environment or to migrate artifacts from another environment.

You cannot 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 (with removeAll=false setting) to restore your environment to a clean state, and then import the backup snapshot.

Note:

The Migration Status Report will not contain historic import and export details if you recreate the 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 Oracle Essbase data and artifacts from an incremental snapshot created by exporting them from another environment.

The Migration Status Report, which is displayed after you initiate the import operation from Lifecycle Management, indicates Failed as the status if the import fails for any reason. Click Failed in the report to open the Migration Details screen, which indicates why the import failed and the corrective action. You can attempt the operation again after correcting the error that caused the import to fail.

About Exports

The Migration Status Report, which is displayed after you initiate the export operation from Lifecycle Management, indicates Failed as the status if the operation fails for any reason. Click Failed in the report to open the Migration Details screen, which indicates why the export failed and the corrective action. In most cases, you can fix the export or backup errors yourself by reviewing the Migration Status Report. You can attempt the export operation again after correcting the error that caused the export to fail.

About Imports

You import snapshots to create a clone of another environment or to migrate artifacts from another environment.

You cannot 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 (with removeAll=false setting) to restore your environment to a clean state, and then import the backup snapshot.

Note:

The Migration Status Report will not contain historic import and export details if you recreate the 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 Migration Status Report, which is displayed after you initiate the import operation from Lifecycle Management, indicates Failed as the status if the import fails for any reason. Click Failed in the report to open the Migration Details screen, which indicates why the import failed and the corrective action. You can attempt the operation again after correcting the error that caused the import to fail.