One of the new requirements of the Exadata Storage Server patches (starting with 18.104.22.168.0) is that the compute nodes will be patched through yum. Previously, the minimal pack was bundled with the storage server patch and applied directly to the database servers. Instead of having the compute node directly receive updates from Oracle's yum repository (the Unbreakable Linux Network - ULN), it is recommended to configure a local yum repository that will download the RPMs from ULN. After this is done, all local servers will connect to the yum repository to receive RPM patches, saving time and network bandwidth. This post will describe how to configure the yum repository on Oracle Enterprise Linux (process borrowed from OTN).
Creating a yum repository does not require any additional license other than a ULN subscription (included with Exadata or any OEL support contract) unlike RedHat's Satellite product, which can be quite pricey. First, you will need a server running Oracle Enterprise Linux. If you don't have anything running OEL, check out Tim Hall's great site - oracle-base.com for a quick primer on installing OEL. After you have a server up and running with OEL, you'll need to register it with the ULN. This requires a CSI - included with an OEL license. To do this, run:
rpm --import /usr/share/rhn/RPM-GPG-KEY
up2date --nox --register
Enkitec Extreme Exadata Expo
Follow me on TwitterMy Tweets
- Exadata 22.214.171.124.1 NFS Issues – Ksplice Support for Exadata?
- 2013 Presentation Schedule
- Oracle Announces Exadata X3-2 and X3-8
- Exadata X3-2 1/8th Rack
- Pre OpenWorld Predictions (Exadata X3-2?)
- Andy Colvin on Exadata 126.96.36.199.1 NFS Issues – Ksplice Support for Exadata?
- Andy Colvin on Exadata V2 Battery Replacement
- Renan Medeiros on Exadata 188.8.131.52.1 NFS Issues – Ksplice Support for Exadata?
- Suleman Naeem on Exadata V2 Battery Replacement
- nasmel on Inside the Oracle Database Appliance – Part 1