On the Manage Database page, you can create and refresh application databases, which are used to store data in Planning for each plan type in the application. Databases are structured according to dimensions, hierarchical members, attributes, and other data specified in an application.
When you create an application, select Create to update the Planning 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 an application are not reflected to users performing data entry and approvals tasks until you refresh the Planning 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:
Currency conversion calculation scripts are updated.
Members and associated properties are propagated from the relational database to the multidimensional database.
Custom attributes are added, modified, or deleted in the multidimensional database.
Exchange rate values are repopulated in the Planning 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 Planning application is restructured.
UDAs are added to the Planning application.
When an administrator uses Create Database or Refresh Database, all other tasks are unavailable to other users.
All users must be logged off from the Planning application before Planning 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 Planning application is refreshed. Planning does not log out users during refresh. See Limiting Use of an Application During Maintenance.
Application refresh time depends on factors such as the number of entities and users in the application, and many users lengthens refresh time. To maximize system availability, you can transfer access permissions information during nonpeak hours.
Watch this video to learn about updating the database in Planning.
To create or refresh the application database:
Database: Creates or refreshes a Planning database for the application.
Update custom-defined functions: Updates Planning custom-defined functions for the application when creating or refreshing the application database.
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.
If this option is cleared, shared members inherit the security assigned to the base member.
To create or refresh data in the Planning database, click Create or Refresh.
Review the confirmation message. To continue, click Create or Refresh. After the update completes, click Finish.