8.5 Updating Oracle Exadata Database Servers

Use the following information and procedures when updating database servers within Oracle Exadata.

• Overview of Oracle Exadata Database Server Updates
  When updating database servers, there is more than one software that needs to be updated.
• Installing, Updating, and Managing Non-Oracle Software
  Installing and updating non-Oracle branded RPMs on Oracle Exadata database servers are allowed as long as kernel and RDMA Network Fabric packages remain untouched.
• Customization Levels and Impact
  
• Update Utility for Exadata Database Servers
  Patchmgr is the update utility for updating Oracle Exadata database servers.
• Update Tool Execution Host
  
• Running the Update Utility as a Non-root User and Running Multiple Invocations Concurrently
  
• Recommended Timeline for Updating Exadata Database Servers
  
• Downloading and Distributing Exadata Database Server Updates
  
• Updating Individual Packages
  
• Running Prerequisite Checks
  
• Backing up Exadata Database Servers Before Planned Maintenance
  Oracle recommends making a backup of the Exadata database servers before making any changes when updating to a next release.
• Running the Update
  You can perform the actual update of Exadata database servers in a rolling (using the --rolling flag) or non-rolling fashion. The default is non-rolling.
• Rolling Back Updates