Restarting a VM for Planned Maintenance
To facilitate maintenance of Oracle Exadata Database Service on Exascale Infrastructure virtual machines (VM), Oracle notifies you of planned VM restarts.
The Oracle Exadata Database Service on Exascale Infrastructure VMs use
underlying physical hosts that periodically must undergo maintenance. When such
maintenance is required, Oracle schedules a restart of your VM, and notifies you of the
upcoming restart. The restart enables your VM to be migrated to a new physical host that
is not in need of maintenance. Stopping and starting the node will also result in the
migration to a new physical host. The only effect to your VM is the restart itself. The
planned maintenance of the original physical hardware takes place after your VM has been
migrated to its new host, and has no effect on your VM. If you do not restart your VM
during the notification period, then Oracle will restart the VM at the end of the
notification period.
Note
You will generally be notified of planned maintenance at least two weeks in advance of the scheduled date, except for time-sensitive situations such as urgent security updates.
When Oracle schedules a restart of your VM, other VMs in that VM Cluster will not be affected by the planned maintenance. The other nodes in your cluster continue to stay available as part of your high availability (HA) strategy.