On the Manage Database page, you can create and refresh application databases, which are used to store data in Essbase for each plan type in the application. Databases are structured according to dimensions, hierarchical members, attributes, and other data specified in applications. Essbase creates an encrypted data file (essbase.sec) to store access permission information.
When you create an application, select Create to update the Essbase multidimensional databases that store application data. While building your outline, you can transfer database changes and access permissions separately to improve performance and make changes quickly available to users. When the outline is complete, Oracle recommends that you include access permissions when refreshing database information.
You must refresh the application database whenever you change the application structure. Changes made to applications are not reflected to users performing data entry and approvals tasks until you refresh the Essbase databases for the application. For example, when you modify properties of an Entity member, add a Scenario, or change access permissions, these changes are stored in the Planning relational database until you refresh the application database.
During refresh:
Essbase security filters are updated.
Currency conversion calc scripts are updated.
Members and associated properties are propagated from the relational database to the Essbase database.
Custom attributes are added, modified, or deleted in the Essbase database.
Exchange rate values are repopulated in the Essbase outline.
Member formulas for certain accounts are dynamically generated or updated.
Additions or changes to alias tables and their associations to dimensions or members are updated.
The Essbase database is restructured.
UDAs are added to the Essbase database.
Caution! | Oracle recommends backing up the application before creating or refreshing. See Backing Up Applications and Application Databases. Following these steps affects data in the database. When you click Create, data is erased and Planning plan types are rebuilt. When you click Refresh, data might be replaced. For important information, see Considerations for Working with Essbase. |
When an administrator uses Create Database or Refresh Database, all other tasks are unavailable to other users, including the application owner. All users must be logged off from the Planning application before Essbase databases can be refreshed. Oracle recommends that administrators send a broadcast message to all users, asking them to save their work and close the application before the Essbase application is refreshed. Planning does not log out users during refresh. See Limiting Use of Applications.
Application refresh time depends on factors such as the number of entities and users in the application, and many users and security filters lengthens refresh time. To maximize system availability, you can transfer access permissions information during nonpeak hours.
To create or refresh the application database:
Back up the application. See Backing Up Applications and Application Databases.
Database: Creates or refreshes an Essbase database for the application.
Update custom-defined functions: Updates Planning custom-defined functions for the application when creating or refreshing the application database. For information about working with custom-defined functions, see the Oracle Essbase Database Administrator's Online Help.
Security Filters: Generates security filters in Essbase for use by third-party applications. Stores access permissions in an encrypted data file (essbase.sec). To generate security filters for all users in the application, select Security Filters, but do not select Validate Limit. To generate security filters for selected users, see Managing Security Filters.
Tip:
Before you generate security filters for all users, limit user access to the application by setting the Enable Use of the Application For option to Administrator. After generating security filters, change the setting back to All Users. See Limiting Use of Applications.
Shared Members: Evaluates access permissions that are set for all instances of the member (base and shared) and applies the least restrictive access permission to them all. For example, if a shared member's parent has Write access assigned to all its children, and another shared member under another parent has Read access assigned to all its children, the base member and all its shared members are given Write access (for examples, see About Effective Access Permissions to Shared Members).
Note:
If your application does not depend on shared member security, consider clearing this option to improve performance.
When this option is cleared, each base and shared member instance uses the member's own security. This means the same cell value could have Read access in one data form and Write access in another data form if each member were selected differently in the respective data forms.
Validate Limit: Identifies security filters that exceed the Essbase security filter limit of 64 KB per row. This option validates filter size to ensure it does not exceed the size limit before building Essbase security filters.
To create or refresh data in the Essbase database, click Create or Refresh.
Review the confirmation message. To continue, click Create or Refresh. After the update completes, click Finish.
Optional: If the create or refresh process takes some time, you can click Run in Background to run the process in the background without displaying the status. To view the results of running Create or Refresh in the background, view the Planning logs. For information about logs, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Troubleshooting Guide.