Difference between revisions of "Patching Exadata"

From dbawiki
Jump to: navigation, search
Line 2: Line 2:
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=1262380.1 Exadata Patching Overview and Patch Testing Guidelines (Doc ID 1262380.1)]
 
* [https://support.oracle.com/epmos/faces/DocumentDisplay?id=1262380.1 Exadata Patching Overview and Patch Testing Guidelines (Doc ID 1262380.1)]
 
* [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 />
 +
It consists of several components:
 +
* Storage Server (containing cell nodes)
 +
* Database Server (compute nodes)
 +
* Infiniband Switches
 +
===Patch order===
 +
Patching it is done on a per-component basis, 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)

Revision as of 16:19, 27 January 2017

Exadata Database Machine is a complete, integrated rack system that contains both hardware and software for running Oracle Database.
It consists of several components:

  • Storage Server (containing cell nodes)
  • Database Server (compute nodes)
  • Infiniband Switches

Patch order

Patching it is done on a per-component basis, 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)