Patching Exadata

• Information Center: Oracle Exadata Database Machine (Doc ID 1306791.2)
• Exadata Database Machine and Exadata Storage Server Supported Versions (Doc ID 888828.1)
• Exadata Patching Overview and Patch Testing Guidelines (Doc ID 1262380.1)
• Oracle Exadata Database Machine Exachk or HealthCheck (Doc ID 1070954.1)
• Exadata patching overview - Pythian

Exadata Database Machine is a complete, integrated rack system that contains both hardware and software for running Oracle Database.

Patch order

Patching it is done on a per-component basis and in general, in this order:

Infiniband Switches

• Spine
• Leaf

Infiniband Switch patches may not be cumulative - needs to be checked in the README.

Storage Server Software

• Cell nodes
• Database Minimal Pack in compute nodes

These patches are usually launched from compute node 1 using dcli and ssh to remotely patch each cell node.
Patches can be applied in a rolling fashion or standalone.
Rolling

./patchmgr -cells <cells group> -patch_check_prereq -rolling
./patchmgr -cells <cells group> -patch -rolling

Standalone

./patchmgr -cells <cells group> -patch_check_prereq
./patchmgr -cells <cells group> -patch

Check the log files:

• /var/log/cellos/validations.log
• /var/log/cellos/vldrun*.log

Database server patch

• Grid Home (if applicable)
• Oracle Home

These patches are specific to Exadata - so download the right ones.
They are, however, installed using the standard opatch mechanism.

CRS MLR patches

• Grid Home
• Oracle Home (if applicable)