Scheduling Content Update Start Time

In Oracle Fusion Cloud Enterprise Performance Management, certain business processes require a content update to incorporate the changes made during the daily maintenance of the environment.

What is Content Update?

Content update propagates the changes introduced during the daily maintenance of an environment. If a content update is required, Oracle creates and schedules a content update job, which will, by default, be executed 3 hours after the daily maintenance is completed. All activities in the environment are suspended while content update is in progress.

If other jobs are active in the environment when the content update job is scheduled to start, the content update job will wait for upto three hours before being rescheduled for the next day. If a similar situation prevails the next day, the content update is forcibly executed during the next scheduled daily maintenance.

Note:

Self-service content update is supported only for Planning Modules, Sales Planning, and Strategic Workforce Planning. Content update for Financial Consolidation and Close and Tax Reporting business processes is performed immediately after completing daily maintenance.

Determine the Content Update Start Time

Service Administrators can control the start time of content update processes by specifying an offset relative to the daily maintenance start time. You can schedule the update to begin any time within a 1 to 12 hour window after the daily maintenance starts. The maximum deferral for the content update is 12 hours, and Oracle will create and schedule the content update job based on your selected settings.

If the content update fails to complete, it will automatically be triggered after the next daily maintenance, bypassing the scheduled time.

If content update fails at any stage, the application enters the administration mode, and only Service Administrator can access it. For example, Oracle performs a cube refresh after the content update, which may fail because of application customizations such as incomplete changes to the outline or metadata that were introduced during the content update. The cause of the failure can be determined by checking the status of the Content Update job. See Handling Pre-Validation Errors.

To solve the failure, Service Administrator can:
  • Sign into the environment and manually remove or finish the updates that caused the failure
  • Run one or more REST APIs to remove or finish the updates that caused the failure
  • Run one or more EPM Automate commands to remove or finish the updates that caused the failure

If a Service Administrator signs into an environment for which content update is scheduled, a screen indicating the scheduled content update is displayed. From this screen, the Service Administrator can start the content update or schedule it for later.

Scheduling Content Update

To schedule content update:

  1. Access an environment as a Service Administrator, or a user with Migrations- Administer role.
  2. Click Tools, then Daily Maintenance, and then Content update scheduling options.
  3. Using Hours and Mins drop down lists, select the offset time for starting the update. This offset is in relation to the daily maintenance start time.

    If daily maintenance is in progress at the content update start time, the environment will wait for the maintenance process to end before starting content update.

  4. To always start the content update at the default update start time, select In the future, automatically update the application content.
  5. Click Save.

Handling Pre-Validation Errors

In case the scheduled content update fails, you will get the following pre-validation error message:

Update of the application content could not start because metadata changes were made and successful cube refresh was not run (but no data is lost)

To view pre-validation errors or check the progress of a content update:

  1. On the Home page, click Application.
  2. Select Jobs, then click Schedule Jobs.
  3. Use the filter options to narrow down your search.
  4. From the Job Type dropdown, select Content Update.
  5. Apply any additional filters as needed, then click Apply.
To resolve pre-validation errors and update content:
  1. Review the job details to identify the corrective actions needed based on the error message.
  2. After addressing the issues, return to Content update scheduling options screen, run a successful cube refresh, and then click Update Now to start the content update.

To postpone the content update until the next maintenance window, click Skip. This will return you to the Home page, and the content update will be rescheduled for the next available maintenance window.

Troubleshooting

See Managing Content Update Issues in Oracle Enterprise Performance Management Cloud Operations Guide.