Note: Simultaneously updating OS and applying Grid Infrastructure patches in rolling fashion is not recommended. Nodes should not be rebooted while GI cluster is in rolling patching mode.
yum update without first stopping Oracle and FlashGrid services may result in the services restarting non-gracefully during the update.
To update OS on a running cluster repeat the following steps on each node, one node at a time
Create backup snapshot of the OS disk
a. Flush OS buffers:
b. Create snapshot of the OS disk /dev/sda1 using AWS console or CLI
Make sure there are no other nodes that are in offline or re-syncing state. All disk groups must have zero offline disks and Resync = No:
If the node is a database node,
a. Stop all local database instances running on the node.
b. Stop Oracle CRS on the node:
# crsctl stop crs
Stop FlashGrid Storage Fabric services on the node:
# flashgrid-node stop
Install OS updates:
# yum update
Reboot the node
# sync; sync
Before updating the next node, wait until the node boots up, all disks are back online, and resyncing operations complete on all disk groups. All disk groups must have zero offline disks and Resync = No before it is safe to update the next node.