Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1576516.1
Update Date:2014-11-07
Keywords:

Solution Type  Technical Instruction Sure

Solution  1576516.1 :   After Upgrading Exadata Software to 11.2.3.2.1 or later, the megaraid_sas*.rpm is no longer installed  


Related Items
  • Exadata X3-2 Hardware
  •  
  • Oracle Exadata Storage Server Software
  •  
  • Exadata Database Machine X2-8
  •  
  • Exadata X3-8 Hardware
  •  
  • Exadata Database Machine X2-2 Hardware
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
  •  
  • _Old GCS Categories>ST>Server>Engineered Systems>Exadata>Patching
  •  


After Upgrading Exadata Software to 11.2.3.2.1 or later, the package megaraid_sas*.rpm is no longer installed.  Is it needed and if so, how do we re-install it.

Applies to:

Oracle Exadata Storage Server Software - Version 11.2.3.2.1 to 11.2.3.2.1 [Release 11.2]
Exadata Database Machine X2-2 Hardware - Version All Versions and later
Exadata Database Machine X2-8 - Version All Versions and later
Exadata X3-2 Hardware - Version All Versions and later
Exadata X3-8 Hardware - Version All Versions and later
Information in this document applies to any platform.

Goal

 After Upgrading Exadata Software to 11.2.3.2.1 or later, the package megaraid_sas*.rpm is no longer installed.  Is it needed and if so, how do we re-install it.

 

Solution

This kernel module RPM package is not relevant and cannot be used by the 2.6.32-400.11.1 (or later) kernels that are now installed following the upgrade to 11.2.3.2.1 (or later).

Additionally, the fix for <bug 14790278> is included in the 2.6.32-400.11.1 (or later), which includes the megaraid_sas module in it's module tree:

Therefore, there is no need for a package to provide an out of tree megaraid_sas module.

The removal of the megaraid_sas-2.6.18-274.18.1.0.1.el5 (or lateer) RPM will have no negative impact on your system.

The missing RPM can be ignored.

References

<BUG:14790278> - SYMANTEC FILE SYSTEM BACKUP UTILITY TRIGGERS CRASH IN DATABASE COMPUTE NODES

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback