Deploying Reporting Databases

A Reporting database is created using the Oracle Essbase Aggregate Storage option (ASO). All calculations are performed through the database outline; and no calculation scripts are required. This option decreases retrieval times and increases scalability.

After you create the Reporting database, the dimension information in the Oracle Hyperion Profitability and Cost Management model is used to generate the aggregate storage outline.

Any errors in the deployment are reported in hpcm.log.

To deploy calculation databases:

1. In an open model, from Task Areas, select Calculate, and then Manage Database.

   The Calculation Database tab of the Manage Database screen is displayed.

2. Select the Reporting Database tab.
   
   
   
3. Under Essbase Information, review the following information:

   • Essbase Server displays the name of the Essbase database server that contains the model.

   • Reporting Application displays the name of the application being deployed.

   • Reporting Database displays the name of the Essbase database to which the application is being deployed.

4. Under Deploy Options, select the Database Options for deploying the calculation database:

   • For the first deployment of a database, all selections are grayed out. This option creates the entire database for the first time.

   • To redeploy an existing database, select Update Database to retain existing artifacts and property settings in the new database, and change the outline to reflect current metadata.

   • For subsequent deployments, select Replace Database to remove the database and applications completely, and recreate them.

5. Under Deploy Options, select the Data Options to be used for the Reporting database deployment:

   • Select Archive Data Before Deploy to export existing data to the application database folder. Only Level-0 data is exported for the Reporting database. For the Reporting database, data is always exported in the native format.

   • Select Archive Data Before Deploy and Reload After Deploy to automatically import the data back into Essbase, using the previously exported data files. A Rules File is not generated for Reporting databases.

     This option is available only if no dimensions are being added or removed. Dimensions can be added or removed in the Profitability Applications Console, or by adding, deleting or changing a stage in Profitability and Cost Management.

     After deleting dimension members, the Archive Data and Reload After Deploy option for redeploying the cube to Essbase and preserving the data is not guaranteed to always work, depending on how Essbase is able to deal with those deleted members. As a workaround, you may have to export all data and remove the data for the deleted members and then reload the data in a separate step after deploying the cube without the Archive Data and Reload After Deploy option selected.

   • Optional: If Archive Data and Reload After Deploy is selected, you can select Delete Data Archive After Reload to automatically delete the archived data only after the successful data reload.

6. Optional: Under Last Reporting Cube Deployed, review the date and time of the previous deployment.
7. Optional: Click Deploy Later to schedule a date and time to run the deployment. See Scheduling Task Flows.

   If this option is not selected when the task is created, you will not be able to schedule the task.

8. Optional: Click Deploy Now to deploy the Reporting database immediately.

   A confirmation message is displayed, indicating that the job has started and identifying the assigned taskflow ID.

   Depending on the size and complexity of the model, this operation may take a significant amount of time.

9. Monitor the progress of the deployment using the taskflow ID, as described in Monitoring Standard Profitability Job Status.