Refreshing the Application Database

The application database, which stores data for each cube in the application, is created when the application is created. You must 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 approvals 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.

Before refreshing the database:

• Back up your application and export data from all databases

• Decide if you want to enable all users or just the current Service Administrator to use the application in administration mode during the refresh

• Decide if you want to log off all users

• Terminate any active application requests

To refresh the database:

1. From the Home page, select Application, and then select Overview.

2. On the Application page, select Actions, and then Refresh Database.

3. On the Refresh Database page, click Create.

4. For Before Refresh Database, select from these options:

   • Enable use of the application for: Lets All users or Administrators (or the current logged in Service Administrator) access the application in administration mode during the refresh

   • Log off all users: Logs off all application users before starting the refresh

   • Stop all active requests: Terminates any active requests in the application before starting the refresh

5. For After Refresh Database, select from these options:

   • Enable use of the application for: Lets All users or Administrators use the application after the refresh.

   • Validate Metadata: When this option is selected, the system scans for member identity (ID) mismatches between the business process and Oracle Essbase and then automatically resolves them after the refresh process. Selecting Validate Metadata might add additional time to the refresh process. For more information, see Validating Metadata.

     Note: The Validate Metadata option is not available for cubes running on the legacy version of Essbase.

6. Click Refresh Database to refresh the database now, or click Save as Job to run the refresh later as a job. See Managing Jobs.

Note:

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