D Backing Up Profitability and Cost Management Components

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

• Operational Data Store

• Import Staging Tables

• Block Storage Option (BSO) Database

Note:

Depending on application type, you may not use some of these databases.

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

Table D-1, 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 D-1 Profitability and Cost Management Database Backup Requirements

Database	Database Type	Backup Options
Import Staging Area	Relational 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 Store	Relational 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 Rules for Standard Profitability only	Oracle Essbase	Standard Essbase backup techniques should be used. For detailed backup and recovery procedures, see the Oracle Essbase Database Administrator's Guide.
Model Data Schema for Detailed Profitability	Relational 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.

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