By Gerry Haskins-Oracle on Jun 10, 2015
Here's an updated version of patching best practice presentation, PatchingBestPractice.pdf.
You can still find more verbose earlier versions in prior postings.
My colleagues in Services are running Best Practice Webinars on knowledge searching and how to find Firmware, Storage updates, and Oracle Solaris patchsets.
The next sessions for patching are this Thursday, Feb 18th, at 9AM MT (U.S. Mountain Time) and 5PM MT. If you miss these, don't worry, there's more being hosted through to the end of April 2011. See below.
Log into MOS and see
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=SYSTEMDOC&id=1282218.1 for details.
Here's the blurb:
I've updated my Patching Presentation for customers, see http://blogs.sun.com/patch/entry/patch_presentation_for_customers
I hope you find it useful.
Also, I forgot to blog about an enhancement we made in March 2010 to the Solaris Update Patch Bundles. The Solaris Update Patch Bundles now add a line to /etc/release when they are installed to make it easier to determine that they've been applied - i.e. that all pre-existing packages on the system have been patched up to the same software level as the corresponding Solaris Update.
On a related note, Oracle 11gR2 requires customers to have Solaris 10 10/08 (Update 6) installed. From Version 188.8.131.52 it will accept the corresponding Solaris Update Patch Bundle as being sufficient to meet this requirement. The modification of /etc/release by the Solaris Update Patch Bundle is partially to help support this.
It's Oracle standard practice to release quarterly Critical Patch Updates (CPUs) containing security fixes. These scheduled releases enable customers to plan maintenance windows.
Solaris now conforms to this practice and Solaris OS CPUs are now available.
The Solaris OS CPU is an archived snapshot of the Solaris OS Recommended Patch Cluster.
Please note that the Solaris OS bug fixing processes have not changed. Security and other bugs continue to be fixed as soon as possible, patches containing such fixes for the Solaris OS will continue to be released as quickly as possible, and they will continue to be included in the Recommended Solaris OS Patch Clusters as soon as they become available.
The Solaris OS CPU simply provides another, archived, patch collation option for customers.
See http://www.oracle.com/technetwork/topics/security/alerts-086861.html and in particular Document 1446032.1 on My Oracle Support (MOS), http://support.oracle.com, which includes CVE mappings for Oracle Sun products.
I'm delighted to announce the availability of 10 new free online patch training modules.
This is the result of a lot of work from those nice people in Sun Learning Services, the Install Revenue Product Engineering (RPE, a.k.a. Sustaining) team, and my own folk.
The modules concentrate on using Live Upgrade for patching, as well as providing background on Deferred Activation Patching, Kernel patches, and other useful information.
You can access the modules as follows:
I think even experienced Sys Admins will find the modules useful in clarifying patching best practices and providing context and background information on the evolution of patching technology and best practices in Solaris 10.
If you don't like the online course format, or if you want a reference document to refer back to after taking the course, please see the attached .pdf.
Best Wishes,Gerry Haskins, Director, Software Patch Services
Ever wanted to run something past a patching expert ?
Want to pick the brains of your peers in other companies ?
Lobby to get a patching enhancement implemented ?
Debate what is an appropriate patching strategy and associated best practices ?
Ask other customers if they are seeing the same issues you are ?
Your wait is over. There are new Patch Forums available to customers with support contracts on http://forums.sun.com.
If you haven't accessed the private contract customer forums on forums.sun.com before, I'm told there's a bit of a "secret-handshake" procedure you must follow for your initial login:
Please note that the above process need only be followed once, in order to register your "Screen Name" for access to the private contract customer forums on forums.sun.com
For all future access, you may go directly to the Patch Forums and login via the "Login" link on the top right of the screen to see the Patch Forum content.
You can use the "Let's talk patching!" Community Forum to discuss Patching Strategy and Best Practices with peers and Sun folk, including potential enhancements to improve your patching experience. It is important to note that this is not an official Support channel. To ensure optimal support, you must continue to raise Service Requests for specific patching issues through the normal support channels, although you may use the Patch Issues sub-forum to see if others have experienced similar issues and know of workarounds or available fixes. As with other forums of this nature, Sun does not guarantee to answer all questions posted. We'd like your feedback on how you would like to see this forum evolve and keep the questions coming so we can better serve your patching needs!
There are two sub-forums available:
Discussions on patching strategies, best practices, news, and potential enhancements to improve your patching experience.
Please note that this is not an official Support channel. To ensure optimal support, you must continue to raise Service Requests for specific patching issues through the normal support channels, although you may use the Patch Issues sub-forum to see if others have experienced similar issues and know of workarounds or available fixes.
I hope you find these forums useful!
They are designed to facilitate dialogue between you and other customers and with Sun subject matter experts to help improve your patching experience.
Best Wishes,Gerry Haskins
This blog is to inform customers about patching best practice, feature enhancements, and key issues. The views expressed on this blog are my own and do not necessarily reflect the views of Oracle. The Documents contained within this site may include statements about Oracle's product development plans. Many factors can materially affect these plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material code, or functionality, and SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISIONS. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle. THIS INFORMATION MAY NOT BE INCORPORATED INTO ANY CONTRACTUAL AGREEMENT WITH ORACLE OR ITS SUBSIDIARIES OR AFFILIATES. ORACLE SPECIFICALLY DISCLAIMS ANY LIABILITY WITH RESPECT TO THIS INFORMATION. ~~~~~~~~~~~~ Gerry Haskins, Director, Software Lifecycle Engineer