Exadata Patching

Recommendations

Info

Storage Server Patches Patch application details Cells utilize software RAID partitions on the first 2 physical disks RAID-1 partitions are created for swap, / boot, /, /opt/oracle, and /var/log/ oracle. / and /opt/oracle have active and inactive partitions Patch is pushed to current inactive partition, then active/inactive partitions are switched
Storage Server Patches Patch apply process 1. Patch contents are copied to /root/_patch_hctap_! 2. New operating system image is pushed to / and /opt/oracle! 3. Cell reboots 4. During cell reboot, exachkcfg service determines if any new firmware updates need to be installed 5. Cell reboots several times to finalize firmware updates 6. Post-installation validation checks are run against the cell 7. Cell usb recovery media is updated to the latest version
Page 1 and 2: Exadata Patching or, “How I Learn
Page 3 and 4: Patching Overview Agenda Patch Appl
Page 5 and 6: Bundle Patches Affect Database and
Page 7 and 8: Infiniband Switch Patches Only inst
Page 11 and 12: OPatch Auto OPatch automation insta
Page 13 and 14: Storage Server Patches Non-rolling
Page 15: Storage Server Patches Applying the
Page 19 and 20: Storage Server Patches Installing C
Page 23 and 24: Mitigating Patching Risks Data Guar
Page 25 and 26: Mitigating Patching Risks OPlan OPl
Page 27 and 28: Mitigating Patching Risks Oplan Out
Page 29 and 30: Patching “Gotchas” No 2 patch a
Page 31 and 32: Horror stories Patching “Gotchas
Page 33: Questions? Andy Colvin, Enkitec Ema

Exadata Patching

Create successful ePaper yourself

Delete template?

Save as template?