Refreshing the Application Database

The application database stores data for each cube in the application. Refresh the database after changing the application structure, and modifying artifacts such as dimensions and members.

Changes made to the application are not reflected to users performing data entry and tasks until the application is refreshed. For example, when you modify properties of a dimension member, add a member, or change access permissions, these changes are reflected to users after you refresh the application. Oracle recommends that you notify all users, asking them to save their work and close the application, before you refresh the database. See Before Refreshing the Database.

You must create a job to refresh the database. You can then submit the refresh database job right away or schedule it to run later.

Creating a Job to Refresh the Database

Submitting or Scheduling a Refresh Database Job

Tip:

When you refresh the application database, all the cubes in the database are refreshed.

For help with troubleshooting database refresh issues, see Troubleshooting Database Refresh Issues.

If your system detects Oracle Essbase outline pre-validation errors during database refresh, see Validating the Essbase Outline.