Patching procedure
- For applying single patches or Release Updates / Patch Set Updates to Grid Infrastructure or Database homes, follow standard procedures documented by Oracle.
- In the case of the FlashGrid cluster, while the GI cluster is in rolling patch mode, do not reboot any nodes, and do not stop FlashGrid services (except for flashgrid_asm.service as described below). Updating OS or FlashGrid software simultaneously with applying Grid Infrastructure patches in a rolling fashion is not recommended.
- Before applying the latest Release Update from Oracle, we recommend requesting confirmation from FlashGrid support. FlashGrid performs validation of every Release Update to minimize the risk of compatibility or reliability issues. The typical time to complete the validation is 3 weeks after the Release Update is publicly available.
- If you have flashgrid-sf package of a version earlier than 26.08 then follow the additional steps describe below during patching of GI home.
Additional steps with flashgrid-sf versions earlier than 26.08
The following additional steps are required during GI home patching only if the version of the used flashgrid-sf package is below 26.08. We recommend updating FlashGrid software to version 26.08 or newer to avoid the need for these additional steps.
To confirm version of the installed flashgrid-sf RPM run: rpm -q flashgrid-sf
On each DB node before applying the patch on that node stop flashgrid_asm.service:
# systemctl stop flashgrid_asm.serviceOn each DB node after applying the patch on that node start flashgrid_asm.service:
# systemctl start flashgrid_asm.serviceNote: The additional steps must be used with both regular and opatchauto patching procedures. Stopping the flashgrid_asm.service will not disrupt storage and can be done safely while Oracle services are still running on the node.