By Gerry Haskins-Oracle on Oct 04, 2013
Here's a Top Tip from my colleague, IPS Guru, and all-round good guy, Pete Dennis:
If the issue(s) addressed by a Solaris 11 IDR (Interim Diagnostics / Relief) are fixed in a subsequent SRU (Support Repository Update), the SRU is said to "supersede" the IDR.
As mentioned in previous posts, in Solaris 11 the IDR is automatically superseded when the system is updated to the relevant SRU (or any later SRU). That is, unlike in Solaris 10, there's no need to manually remove the IDR before updating*. We provide "terminal packages" for superseded IDRs in the Support Repo, enabling IPS (Image Packaging System) to automatically handle the IDRs for you.
Several weeks before a planned maintenance update, it's a good idea to check whether all the IDRs in use are superseded by the SRU to which you are planning to update.
If any of them aren't superseded, and the relevant packages they touch are updated in the SRU, you'll need to raise an SR (Service Request) with Oracle Support to get new IDRs generated for the relevant BugIDs at that SRU level. So please ensure you provide enough time for these to be generated. Note, if the Bugs are already fixed in a later SRU, you'll be told to update to that SRU.
Is there a simple way for a customer to find out which of their IDRs will be superseded by updating to a given SRU ?
All superseded IDRs are tagged in the Support Repository and on the
incremental ISO images available from MOS (My Oracle Support).
The following command will list the superseded IDRs in the Support Repository, so you can then examine the ones of interest.
I'm assuming here that you're maintaining a local Repo behind your firewall which is, at a minimum, up to date with the SRU to which you are planning to update:
pkg list -g http://<url of local repo> -af idr*
pkg contents -g http://<url of local repo> -m idr679
set name=pkg.fmri value=pkg://solaris/idr679@3,5.11:20130905T193900Z
set name=pkg.description value="Terminal package"
set name=pkg.renamed value=true
depend fmri=pkg:/email@example.com,5.11-0.175.1.11.0.4.2 type=require
You do need to be able to interpret FMRI strings correctly (see previous posts). For example, 5.11-0.175.1.11.0.4.2 is Solaris 11.1 SRU 11.4 or, to give it its official Marketing name, Solaris 18.104.22.168.0.
So that tells us that idr679 is superseded by Solaris 11.1 SRU 11.4 (Solaris 22.214.171.124.0).
We'll look to make this more transparent by adding a text field with the human readable translation of the FMRI string to the metadata.
If you wish to restrict updates to selected SRUs which you have "qualified" in your environment, for example, a "Golden Image", Bart's blog posting may also be of interest.
* There's more work required to make this happen seamlessly in Solaris 11 Zones.