Difference between revisions of "Patching Exadata"
From dbawiki
(→Storage Server Software) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | * [https://support.oracle.com/epmos/faces/DocumentDisplay? | + | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=1187674.1 Information Center: Oracle Exadata Database Machine (Doc ID 1306791.2)] |
| + | * [https://support.oracle.com/epmos/faces/DocumentDisplay?id=888828.1 Exadata Database Machine and Exadata Storage Server Supported Versions (Doc ID 888828.1)] | ||
* [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://support.oracle.com/epmos/faces/DocumentDisplay?id=1070954.1 Oracle Exadata Database Machine Exachk or HealthCheck (Doc ID 1070954.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 /> | Exadata Database Machine is a complete, integrated rack system that contains both hardware and software for running Oracle Database.<br /> | ||
| Line 8: | Line 10: | ||
* Spine | * Spine | ||
* Leaf | * Leaf | ||
| + | Infiniband Switch patches may not be cumulative - needs to be checked in the README. | ||
| + | |||
====Storage Server Software==== | ====Storage Server Software==== | ||
* Cell nodes | * Cell nodes | ||
| Line 27: | Line 31: | ||
* /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) | ||
Latest revision as of 09:59, 6 February 2017
- 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.
Contents
Patch order[edit]
Patching it is done on a per-component basis and in general, in this order:
Infiniband Switches[edit]
- Spine
- Leaf
Infiniband Switch patches may not be cumulative - needs to be checked in the README.
Storage Server Software[edit]
- 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[edit]
- 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[edit]
- Grid Home
- Oracle Home (if applicable)
