Daily Maintenance Operations

Every day, during the operational maintenance of the enviroment, Oracle does the following:

  • Create maintenance snapshot called Artifact Snapshot of existing artifacts and data. See Backing Up and Restoring an Environment Using the Maintenance Snapshot.
  • Apply any required patches (for example, monthly updates, weekly patches, one-off patches)
  • Adjust configurations, such as caches
  • Analyze all the activities performed and logs created during the last 24 hours and create the Activity Report

Following this, the environment is rebooted, with initial access only to Service Administrators as the maintenance process continues with database backup.

Unavailable Operations During Daily Maintenance

During this period, some business processes, like Oracle Enterprise Data Management Cloud, have all operations restricted while specific operations are limited for other processes. Refer to the table below for details:

Business Processes Operations Not Available
Account Reconciliation All import and data integration operations
Planning
  • Clear Cube
  • Compact Outline
  • Data Integration
  • Export Data
  • Export Metadata
  • Import Data
  • Import Metadata
  • Merge Data Slices
  • Optimize Aggregation
  • Refresh Database
  • Restructure Cube
Enterprise Profitability and Cost Management
  • Clear Cube
  • Compact Outline
  • Data Integration
  • Export Data
  • Export Metadata
  • Import Data
  • Import Metadata
  • Merge Data Slices
  • Optimize Aggreration
  • Refresh Database
Financial Consolidation and Close
  • Data Integration
  • Export Data
  • Export Metadata
  • Import Data
  • Import Metadata
  • Refresh Database
  • Restructure Cube
Oracle Enterprise Data Management Cloud All operations
Narrative Reporting None
Profitability and Cost Management
  • Application - Calculation Rules
  • Application - Dimension Management
  • Dashboards
  • Data Integration
  • Intelligence - Analysis Views
  • Models - Designer
  • Models - Execution Control
Tax Reporting
  • Data Integration
  • Export Data
  • Export Metadata
  • Import Data
  • Import Metadata
  • Refresh Database
  • Restructure Cube

Note:

  • Operations for Planning, Enterprise Profitability and Cost Management, Financial Consolidation and Close, and Tax Reporting are restricted during Daily Maintenance, if invoked through EPM Automate or REST API or scheduled through Job Console. They can be invoked manually from the Job Console, if the user can login.
  • Nothing is completely blocked for Profitability and Cost Management during the entire daily maintenance duration. These operations are blocked partially.
    • Dimension Management, Dashboards, and Analysis Views are temporarily blocked for a few seconds to over 30 minutes (depending on the dimension members in the application), immediately after the service restarts.
    • Calculation Rules, Designer, and Execution Control are blocked after the above operations are available, for a few seconds to potentially an hour, depending on the number of rules in the application. Notably, during this duration, Rule operations (such as Designer, Calculation, etc.) become incrementally available based on the specific POV requested by the application.

Default Maintenance Start Time

Because environments are not available to users during the maintenance window, the Service Administrator should identify a one-hour period when no one uses the service. Any connected user will be logged off and unsaved data will be lost.

The default maintenance start time is between 10:00 p.m. and 1:00 a.m. local time of the data center that hosts your environment. If you do not reset the default start time for an environment, Oracle randomizes it to start between 10:00 p.m. and 1:00 a.m. local time of the data center. After you select a maintenance start time, Oracle honors your selection. See Setting the Maintenance Start Time for an Environment.

Some services may perform additional maintenance operations. For example, Planning Modules, Account Reconciliation, and Financial Consolidation and Close may require additional maintenance time for content upgrade.

Additionally, because of planned daily maintenance, the status of the environment in My Services console is always displayed as Planned Maintenance (in yellow) even if your environment has no other planned maintenance for the day.


EPM Cloud Impacted status

Note:

To allow users to save their data, Oracle Enterprise Performance Management Cloud displays a notice of impending maintenance 15 minutes before the maintenance process starts.

Inform Users of Daily Maintenance Completion

Though EPM Cloud has marked one hour for Daily Maintenance, it usually takes much lesser time to complete. You can use a custom script to inform users that daily maintenance is complete so that they can resume their activities. See Inform Users of Daily Maintenance Completion in Working with EPM Automate for Oracle Enterprise Performance Management Cloud.