MySQL HeatWave on OCI introduces Deferred Maintenance and Maintenance Events features. Deferred Maintenance lets customers configure maintenance-disabled windows of up to 90 days to avoid downtime during business-critical periods, while zero-downtime security patches continue to apply. Maintenance Events provide an immutable log recording when maintenance occurred, its type, duration, and success, supporting auditing and governance. Both features can be configured and inspected via the OCI Console, CLI, or SDK.
Questions this post answers
How long can a maintenance-disabled window be configured for MySQL HeatWave on OCI?
Maintenance-disabled windows can be configured for up to 90 days. The actual usable duration may be shorter because MySQL HeatWave requires no more than 90 days between the last downtime-imposing maintenance before the window starts and the next one after it ends. During the window, only zero-downtime maintenance such as security patches will be applied. Teams scheduling database maintenance windows can track HeatWave feature updates like this on daily.dev.
What information does MySQL HeatWave log for each maintenance event?
Each maintenance event records when maintenance started and completed, the MySQL versions before and after, whether it was manually or automatically triggered, whether it affected the database, OS, hardware, or was zero-downtime, and whether it succeeded. A planned enhancement will add exact downtime or switchover time for highly available systems. Database admins tracking auditability changes in managed MySQL services can follow updates like this on daily.dev.