How Does Downtime Affect Scheduled Processes That Were Already Submitted?

When the application goes down in maintenance mode, no scheduled processes will run during the downtime. Take note of when maintenance will happen so that you can prepare and plan ahead.

It's a good idea to ensure that you and your users follow these best practices:

• Avoid submitting long-running processes before the downtime.
• In general, put on hold any processes that are still running before the downtime, then release them after the downtime is over. If you know the reasons for the downtime, here are additional considerations:
  • Release update: You don't need to put all processes on hold, but it's recommended.
  • Cloning or migration: No need to put processes on hold, since processes will be deleted from the target environment.
  • Oracle Analytics Publisher server bounce: You don't need to put all processes on hold.
• Avoid submitting any processes during the downtime.

Here's what happens before, during, and after the maintenance period:

• Starting 3 hours before, and during the entire downtime, you will see a message in the Scheduled Processes work area about the maintenance. Don't submit any processes while you still see this message.
• During a grace period of 5 minutes before the downtime starts, any processes that are still running might be automatically paused. But if they're not, then those processes end with a Canceled status after the grace period.
• No processes run during the downtime. If a process was submitted on a recurring schedule and was supposed to run during the downtime, it doesn't run at the scheduled time but right after the downtime ends.
• Any processes that were automatically paused during the downtime resume running after the downtime ends.