Exadata Patching

Recommendations

Info

Horror stories Patching “Gotchas” Minimal pack installation failed on one database server, and it wouldn’t boot up completely Messages were received regarding missing kernel modules, and the system was not able to bring up network interfaces Only access was through KVM or ILOM’s serial console Discovered that the minimal pack had wiped out the listing of kernel modules in /lib/modules/ before backing it up Solved the issue by formatting a USB stick with ext3 and copying modules over from the surviving compute node Database servers now back up these files before applying a minimal pack
Horror stories Patching “Gotchas” Cell would not start back up with correct IP address entries After applying the Exadata storage software patch, the cell would start up with the IP address settings from the factory Manually recreating the network interfaces would not persist after a reboot Issue was traced back to a corrupted /opt/oracle.cellos/cell.conf file. After recreating this file with the correct values, the network settings stayed correct after reboots Oracle now recommends in the patch README to run ipconf –dry before issuing a storage server patch
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 and 16: Storage Server Patches Applying the
Page 17 and 18: Storage Server Patches Patch apply
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: Patching “Gotchas” No 2 patch a
Page 33: Questions? Andy Colvin, Enkitec Ema

Exadata Patching

Create successful ePaper yourself

Delete template?

Save as template?