By Tammybednar-Oracle on Mar 01, 2016
The next ODA Patch 188.8.131.52 is going to provide in-place upgrade of the operating system from OL5.11 to OL6.7. As many of you may know, it was not an easy upgrade to OL6 as it required your systems to be re-imaged. Our ODA team did not feel this was a good thing to require a re-image of your ODA, so we have engineered the upgrade to be in-place and rolling.
However, before you jump into the air and yell hurrah, this patch requires the ODA to first have the 184.108.40.206 patch applied successfully. So for those of you that have not upgraded your ODA’s in a while or are on a version less than 220.127.116.11.0, please review the README (https://updates.oracle.com/Orion/Services/download?type=readme&aru=19485583) of the 18.104.22.168 patch set as you may need to apply an interim patch before moving to 22.214.171.124.
The 126.96.36.199 patch does not apply updates to the ILOM, BIOS, Controller, Expander, or disk firmware. So, before you patch your ODA to 188.8.131.52, run the oakcli command with the 184.108.40.206 version/patch
oakcli show version -detail
All of the components, except the databases, should show Up-To-Date. The installed versions vary from ODA HW versions...it is the UP-TO-DATE that you are looking for.
|Component Name||Installed Version||Proposed Patch Version|
After your ODA is patched up-to-date with 220.127.116.11, continue to prepare for the 18.104.22.168 patch using the pre-check tool. It will verify if you have enough free space in /u01, verify RPMs that have been added, and verify RPMs that are expected.
This means that if you have 3rd party agents running on ODA and had to install RPMs from OL5, you will have to re-install the OL6 RPMs to support those agents after the upgrade.
For the pre-check tool, download the ZIP file from here. Upload it to both of your ODA nodes to a directory, /tmp works just fine. Unzip the file and run the command
You can check the currently installed RPMs using "rpm -qa" command or you may want to use “rpm –qa –last” to see the latest RPMs that were updated since the last upgrade.
In addition, here are some best practices for patching on ODA .
- Check ALL disks / diskgroups and make sure that they are all online and healthy. For a good disk level check for ASM, OS and multipath:
- · Make sure the ODA patch level matches on both nodes.
- Check CRS and connectivity before patching. Make sure CRS, ASM and OAK are running on both nodes.
- Check OS based storage. Clean up as needed including older installations if you have upgraded previously.
- - 10GB of free space min. on each node (/u01 and / )
- Run an oracheck report
- Review 888888.1 for known issues
o Fix or replace any disks before considering upgrading
o If your ODA version is 2.10 or lower for your source make sure you check compatibility with the new disk - See ODA + HGST based notes)
show version -detail
oakcli validate -d on each node