Setting the Daily Maintenance Process Time

Understand how to determine and set the most convenient time to start the hour-long daily maintenance process.

A business process instance requires one hour every day to perform routine maintenance. Service Administrators can select (and change) the most convenient time to start the hour-long daily maintenance process. In addition to routine maintenance, Oracle applies required patches to the business process instance during the maintenance process.

Because the business process instance isn't available to users during the maintenance process, the Service Administrator should identify a one-hour period when no one uses the business process. Any connected user will be logged off and will lose unsaved data.

The default maintenance start time is midnight Pacific Standard Time (PST). If you don't reset the default start time for your instance, Oracle resets it to a random time between 10:00 p.m. and 2:00 a.m. PST to reduce the business process maintenance duration.

Note:

If you really want the maintenance time to start at midnight PST, you should select it using this procedure. In such cases, Oracle will not change your selection.

To manage the automated maintenance window:

  1. Access a business process instance.
  2. Tap or click Tools and then Daily Maintenance.
  3. In Start Time, select the time at which the daily maintenance process should start. Also, select your time zone from the drop-down list.
  4. Click Apply.

For high volume data customers, the hour-long daily maintenance process may not be long enough to complete a full data export.

The Export EPM Cloud Smart List textual data during daily maintenance for incremental data import application setting, when enabled, exports the Essbase data plus the Planning member-driven Smart List intersections with their corresponding text labels during the daily maintenance process. This export can be lengthy because the system has to find all the possible intersections, uniquely identify their mappings, and then extract them.

The advantage to exporting the data for Planning member-driven Smart Lists in the daily maintenance process is that you can use the data later for an incremental (or selective) data load. However, the Planning member-driven Smart List data is not needed to restore your system.

To improve the maintenance process time for those customers who are experiencing lengthy data exports, you can disable the Planning member-driven Smart List data export during the maintenance process, thus only backing up the data needed to perform a full restoration.

Application setting: Export EPM Cloud Smart List textual data during daily maintenance for incremental data import

  • Yes—Performs a complete export during the daily maintenance process, such that data, including the Planning Smart List data, can be incrementally imported to an application (this option may lengthen the maintenance process duration)

  • No (default)—Creates an application backup during the maintenance process, such that data can be used as part of a full restoration

To view and change this setting, see What Application and System Settings Can I Specify?

Caution:

  • If No is selected, the data portion of the backup does not have Planning Smart List data, so using the backup to perform an incremental (or selective) data load can lead to data loss.

  • Importing only the Essbase portion of the data from a full maintenance process snapshot is problematic.

If you routinely use the maintenance process export for incremental data imports and are comfortable with the length of the current daily maintenance process, we recommend that you set the option to Yes. Otherwise, keep the default option (No) and perform a separate data export using the Migration user interface. Data exported during a migration can be used to perform an incremental data import, but keep in mind that since this export includes the Smart List data, the export duration can be lengthy depending on the data volume.