Creating a Job to Refresh the Database

To create a job to refresh the database:

  1. From the Home page, click Application, and then click Jobs.

  2. Click the App Maintenance tab at the bottom of the Jobs console.

  3. On the App Maintenance tab, click Create Job.

  4. In Job Type, click the drop-down and select Refresh Database.

  5. In Job Details, enter a name for the Refresh Database job, and enter details about what to do before and after refreshing the database.

    Before Refresh Database

    • 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.

    After Refresh Database

    • 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.

      The Validate Metadata option is available for cubes with these storage options running on the Oracle Essbase version that supports Hybrid Block Storage Option (BSO) cubes: Hybrid BSO, ASO, and BSO. This option is not available for cubes running on the legacy Essbase version that does not support Hybrid BSO cubes.

      Note:

      For the first cube refresh after upgrading from non-hybrid to Hybrid Essbase, enable the Validate Metadata option (either immediately or later as a scheduled job). For examples of potential errors during validation and how to address them, see Validating the Essbase Outline in Getting Started Guide for Administrators.

    • Execute Application Diagnostics: When this option is selected, Application Diagnostics automatically runs during the Refresh Database process.

      The Execute Application Diagnostics setting is saved with a database refresh job and retained when the job is edited or rerun. If enabled, the job progress includes a Generating Application Diagnostics Report step. After the job completes, the Jobs console displays the refresh and diagnostics results, along with the report name if generated successfully.

      Note:

      Application Diagnostics is an optional validation step. It does not change the outcome of the database refresh. If the refresh fails, the overall job is reported as failed even if diagnostics completes successfully.

  6. Click Save to save the information about the Refresh database job.