Difference between revisions of "Patching Exadata"
From dbawiki
(→Patch order) |
|||
| Line 3: | Line 3: | ||
* [https://www.pythian.com/blog/exadata-patching-overview/ Exadata patching overview - Pythian] | * [https://www.pythian.com/blog/exadata-patching-overview/ Exadata patching overview - Pythian] | ||
Exadata Database Machine is a complete, integrated rack system that contains both hardware and software for running Oracle Database.<br /> | Exadata Database Machine is a complete, integrated rack system that contains both hardware and software for running Oracle Database.<br /> | ||
| − | |||
| − | |||
| − | |||
| − | |||
===Patch order=== | ===Patch order=== | ||
Patching it is done on a per-component basis and in general, in this order: | Patching it is done on a per-component basis and in general, in this order: | ||
Revision as of 16:23, 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
Database Bundle Patch
- Grid Home (if applicable)
- Oracle Home
CRS MLR patches
- Grid Home
- Oracle Home (if applicable)
