Difference between revisions of "Patching Exadata"
From dbawiki
(→Storage Server Software) |
(→Database Bundle Patch) |
||
| Line 27: | Line 27: | ||
* /var/log/cellos/vldrun*.log | * /var/log/cellos/vldrun*.log | ||
| − | ====Database | + | ====Database server patch==== |
* Grid Home (if applicable) | * Grid Home (if applicable) | ||
* Oracle Home | * Oracle Home | ||
| + | These patches are specific to Exadata - so download the right ones.<br /> | ||
| + | They are, however, installed using the standard opatch mechanism. | ||
| + | |||
====CRS MLR patches==== | ====CRS MLR patches==== | ||
* Grid Home | * Grid Home | ||
* Oracle Home (if applicable) | * Oracle Home (if applicable) | ||
Revision as of 16:57, 27 January 2017
- Exadata Information Center (Doc ID 888828.1)
- Exadata Patching Overview and Patch Testing Guidelines (Doc ID 1262380.1)
- Exadata patching overview - Pythian
Exadata Database Machine is a complete, integrated rack system that contains both hardware and software for running Oracle Database.
Contents
Patch order
Patching it is done on a per-component basis and in general, in this order:
Infiniband Switches
- Spine
- Leaf
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)
