Backing Up Profitability and Cost Management Components

There are several Profitability and Cost Management databases that need to be backed up on a regular basis to ensure the safety and integrity of your data:

The frequency of backup is determined by the amount of change in the databases, and the general standards of your organization.

Table 12, Profitability and Cost Management Database Backup Requirements, lists the databases that must be backed up, their type, and suggested backup options.

Caution!

Lifecycle Management (LCM) cannot currently be used to back up the import staging area or the operational data store.

Table 12. Profitability and Cost Management Database Backup Requirements

DatabaseDatabase TypeBackup Options
Import Staging AreaRelational Database (RDB)Standard backup techniques for any RDB can be used, including the following options:

  • Database scripting

  • Scheduler scripts

  • Backup tools, such as TOAD

  • Backup procedure from SQL Server or Oracle.

Operational Data StoreRelational Database (RDB)Standard backup techniques for any RDB can be used, including the following options:

  • Database scripting

  • Scheduler scripts

  • Backup tools, such as TOAD

  • Backup procedure from SQL Server or Oracle.

Block Storage Option (BSO) and Aggregated Storage Option (ASO) Database and Assignment RulesEssbaseStandard Essbase backup techniques should be used. For detailed backup and recovery procedures, see the Oracle Essbase Database Administrator's Guide.

For detailed backup and recovery procedures, see the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide.