Oracle 188.8.131.52 is Now Available for Exadata
Jan 3, 2012 / By Marc Fielding
Since Oracle 184.108.40.206 came out last September, there have been questions about Exadata availability. As of today, the patchset is now available.
Reviewing the upgrade document (MOS note 1373255.1) a few things that jumped out at me:
- There is already a bundle patch (220.127.116.11 BP1, patch 13343057) that must be installed directly after the DB upgrade
- If running 18.104.22.168, a bugfix for unpublished bug 12539000 Synchronization problem in the IPC state affects ASM rolling upgrade and is required. BP12/13 have it (though the installer will still complain and must be ignored on install), and there are backports for BP7 through BP11.
- A recent storage server version (22.214.171.124.0+) is required, though with the critical issues fixed in 126.96.36.199.2, An upgrade there is probably in order.
- Install happens in a new ORACLE_HOME that should not be under /opt/oracle (presumably due to storage space limitations)
- Automatic memory management must be permanently disabled in the ASM instance, in favor of fixed SGA and PGA targets. Keep in mind that AMM would have prevented ASM from using hugepages in the past, and should be explicitly disabled with use_large_pages as part of the change.
- As for other database version upgrades, the data dictionary update requires system-wide downtime, though this can be minimized using a logical standby or GoldenGate.
Hat tip to R. Kundersma’s blog for the notification.
2 comments on “Oracle 188.8.131.52 is Now Available for Exadata”
Pingback: Introducing the Quarterly Database Patch for Exadata | The Pythian Blog