1. Administering Migration for Oracle Enterprise Performance Management Cloud
  2. Using Migration
  3. Backing up Artifacts and Application
  4. Backup Application

Backup Application

Use Backup to create a snapshot that can be used to clone an environment, for example to migrate an application from a production instance to a test instance for troubleshooting or additional development work.

When you backup the environment, you create a snapshot of the entire environment, similar to the daily maintenance snapshot, by exporting the application with all of its data and artifacts. Backups include artifacts belonging to Document Repository, Core (previously labelled Planning), Data Management, Calculation Manager, and Groups and Membership. Artifacts in Core includes Relational and Essbase data, global and security artifacts, configuration and plan type artifacts, etc. required for the current application. Please note that the availability of artifacts belonging to these categories is governed by the application in the current environment.

Backup of Essbase Data

Oracle Essbase data backups are performed with Essbase shut down (cold backup). To prevent potential data corruption, before starting the Essbase data backup, shut down all processes (consolidation, restructure, and so on) that modify ASO and BSO cubes.

Backup for Planning Only

The backup process exports data associated with member driven smart lists, if any, enabled in Aggregate Storage (ASO) cubes. Depending on the number of such members enabled for ASO, the cube design, and the amount of data the generated MDX query to export data may contain deep cross-join sections that may cause the backup process to fail with a memory allocation error.

Always use the daily maintenance snapshot to restore Planning environments.

Backup for Enterprise Journals

While migrating from test to production environment, do not include the following:
  • JOURNAL_ID (accessed by selecting Enterprise Journals, then Dimensions and then JOURNAL_ID.
  • Collection Interval Data (accessed by selecting Enterprise Journals, and then Collection Interval Data.
However, you should include Teams data if you have defined Teams in the source application (accessed by selecting Close Tasks and then Teams.

Backup for Data Management

The LCM Mode setting in Data Management gives the Service Administrator the control to backup and export of staging table (Workbench) data. The export of data can be a lengthy process depending on the LCM Mode setting and at this time the system goes into maintenance mode.

  1. Before you migrate staging table data, create a baseline snapshot. The baseline snapshot is required to select options to add data to incremental snapshots.

    To create the baseline snapshot, in Data Management, select All as the Snapshot Type value.

  2. Incremental snapshots created using the default export settings do not contain staging table data. To export and import this data, specify the required export settings in Data Management. Specifically, select Single Snapshot – Setup and Data as the value of the LCM Mode option.
For detailed steps, see these sources in Administering Data Management for Oracle Enterprise Performance Management Cloud:

Backup for Oracle Enterprise Data Management Cloud

The application is placed into maintenance mode when you create a backup snapshot.

Troubleshooting

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