My Oracle Support Banner

Strategies To Avoid Conflicts Between A Maintenance Window and Batch Processes (Doc ID 2834594.1)

Last updated on MARCH 28, 2024

Applies to:

MySQL Database Service - Version N/A to N/A
Information in this document applies to any platform.


An automatic maintenance done during the maintenance window and batch processes are typically scheduled at night to avoid the busiest hours. Daily batch processes tend to be scheduled at night, too. This causes some conflicts; a batch process can be interrupted by an automatic maintenance, because it involves restarts of the database instance. Since an automatic maintenance cannot be avoided, a user must cope with upcoming maintenance, even if it's done infrequently. If a batch process can be suspended on a certain day of week, they will not be conflict, and there's no problem. Otherwise, it is necessary to cope with those conflicts.

This document describes some strategies to prevent batch processes from interrupted by a maintenance.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Adjusting time schedules
 Monitor events
 Make the batch processes retryable, keep each transaction size small

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.