My Oracle Support Banner

Exadata YUM Repository Population, One-Time Setup Configuration and YUM upgrades (Doc ID 1556257.1)

Last updated on FEBRUARY 23, 2024

Applies to:

Oracle Exadata Storage Server Software - Version 11.2.1.2.0 and later
Linux x86-64

Goal

NOTE: This note has become obsolete and is not maintained. 

  • <document 1473002.1> should be followed for updating Exadata DB nodes currently on releases 11.2.2.4.2. or later
  • When running Exadata Images older than 11.2.2.4.2, first update to 11.2.2.4.2 following the README instructions in <patch 13513611>. When required also update the Linux Operating system from 5.3 to 5.5 following <document 1284070.1> 

 

As of Oracle Exadata Storage Server Software 11g Release 2 (11.2) 11.2.3.1.0, the minimal pack has been discontinued. The Linux database server update procedure uses the Unbreakable Linux Network (ULN) for the distribution of the updates. The updates are now packaged as several rpms and the Linux YUM utility is used to apply the updates. This document will describe the following steps in this process:

NOTE: This document should be used for applying Exadata release 11.2.3.2.0 and higher on existing Exadata releases running version 11.2.1.2.0 or higher. Use the command 'imageinfo' to find out what release your database server is running. When patching a node it's highly recommended  to create a backup first using the backup script "dbserver_backup.sh"

How to use this note

Depending on the Exadata Storage Software release currently running on your database nodes, you should review particular sections of this note. Regardless of your current release, you should review sections 1 through 4 and sections 7 through 9 as they will assist in ensuring a successful patching session. 

Regardless of your current release, you must create a local yum repository to contain the Exadata ULN channel contents.  To complete the repository creation process, you will execute the steps in Section 3 "Preparing and Populating the yum Repository Server".  These steps can be done without downtime to the databases and applications on the database nodes and should be done well prior to the actual database node upgrade to reduce impact to application availability.

If your current release is 11.2.2.4.2 or earlier, you must perform an initial setup of the database node to allow for patching with yum and using the Exadata ULN channels.  To perform both the initial setup and the actual upgrade, you will execute the steps in Section 5 "Performing One-Time Setup on Database Servers of Oracle Exadata Database Machine".  Once these steps are completed successfully and all database nodes show the correct release in the imageinfo command, you are done with the patching session.

If your current release is 11.2.3.1.0 or later, the database node will already be configured to patch using yum and the Exadata ULN channels.  To perform the upgrade, you will execute the steps in Section 6 "Updating Database Nodes previously patched or freshly imaged to 11.2.3.X.X".  Once these steps are completed successfully and all database nodes show the correct release in the imageinfo command, you are done with the patching session.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
 How to use this note
Solution
 1. Introduction
 2. Information table
 3. Preparing and Populating the yum Repository Server
 The following procedure details how to prepare and populate the yum repository server.  
 1. Ensure you have the following prerequisites for registering for ULN:
 2. Set up and register the yum repository server to ULN as follows:
 3. Log in to ULN at one of the following URLs:
 4. Navigate to the Systems tab. 
 5. Click the yum repository server registered in step 2. 
 6. Click Edit to edit the yum repository server properties. 
 7. Check the Yum Server check box and click apply changes.
 8. For 64-bit Oracle Linux 5 systems, subscribe to the Oracle Exadata and other essential ULN channels as follows:
 9. Create the yum repository as follows:
 10. Populate the repository as follows:
 11. Make the repository available on the HTTP server for access by the database servers that will use the repository for the yum updates.
 12.  Identify the repository URL for the Oracle Exadata channel.
 The following procedure details how to use ISO as the yum repository server.
 4. Backing up Database Servers
 5. Performing One-Time Setup on Database Servers of Oracle Exadata Database Machine
 About the Helper Scripts
 Performing the One-Time Setup steps
 1. Set the database server offline for the duration of this procedure. Other servers in the cluster can remain up and running 
 2. If the database server is using Oracle Linux 5.3 kernel, ensure you have followed steps 1-4 as described in My Oracle Support note 1284070.1 to prepare for the Linux update:
 3.  Performing a backup
 4. Executing the bootstrap scripts
 5. Relink the Oracle software components as documented in the Maintaining Oracle Database Servers section in the Exadata Database Machine Owners Guide.
 6. Startup the stack
 6. Updating Database Nodes previously patched or freshly imaged to 11.2.3.X.X
 1. Create a backup now
 2. Update or create a /etc/yum.repos.d/Exadata-computenode.repo file
 3. Update yum.conf
 4. Set the database server offline for the duration of this procedure. Other servers in the cluster can remain up and running 
 5. Empty the yum cache using the following command:
 6. Verify the yum repository using the following command:
 7. Remove rpm's (if installed):
 8. Update the database server using <channel as mentioned in the patch README>.
 9. For NON-X2-8 and NON-X3-8 ONLY: Remove rpm’s using the following command:
 10. Clean the yum cache:
 11. Relink the Oracle software components as documented in the Maintaining Oracle Database Servers section in the Exadata Database Machine Owners Guide.
 12. Startup the stack
 7. Rolling Back Software Changes 
 8. Optional: Removing Nonessential rpms
 9. RPM, ULN and yum troubleshooting
 Conflicting RPM's
 Connecting the YUM Repository Server to ULN by Proxy
 Steps after mistakenly removing packages before "yum update" was executed
 Revision History
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.