Guess I didn't understand that was the purpose of --minimal. So based on your answer, there is no way to follow the Oracle Best Practices patch strategy of applying the CPU between update releases using pca? Except maybe grabbing the patchdiag.xref on the day the CPU is released and comparing the patch revisions between patchdiag and the CPU?<div>
</div><div><br><div class="gmail_quote">On Fri, May 27, 2011 at 4:59 AM, Don O'Malley <span dir="ltr"><<a href="mailto:don.omalley@oracle.com">don.omalley@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
Hi Jeff,<br>
<br>
The --minimal option never mapped to the contents of the CPU.<br>
<br>
The --minimal option is mapped to the Recommended Patch Cluster
contents, not the CPU. The CPU is effectively an archived version of
the Recommended Patch Cluster, so the 2 are closely related. <br>
That said, with changes that we made to merge the Recommended Patch
Cluster and former Sun Alert Cluster (see <span></span><a href="http://blogs.oracle.com/patch/entry/merging_the_solaris_recommended_and" target="_blank">Patch Corner - Merging the Solaris Recommended and Sun
Alert Patch Clusters</a> for the details), we now only add the lowest
revision of a patch required to address SunAlert issues (Security, Data
Loss and System Availability).<br>
This means that over time customers need to apply less patches to keep
up to date with critical fixes.<br>
<br>
This is the reason that some patches in patchdiag.xref that are
Recommended are now longer the latest revs of patches.<br>
<br>
The only exception to this rule is patches required for the patch
utilities on Solaris to function correctly; these patches (eg. 119254)
are always kept at the latest available revision.<br>
<br>
HTH,<br>
-Don<div><div></div><div class="h5"><br>
<br>
<br>
Jeff wrote:
<blockquote type="cite">I've been using the --minimal option for pca since it came
out to standardize patching based on the most recent CPU. Today I
noticed that is looks like Oracle dropped support for in in
patchdiag.xref.<br>
<br>
I'm using the patchdiag.xref I downloaded on May 15th and trying to
apply the patches from the April/2011 CPU using pca. I find these
patch discrepancies between what is in the CPU and what is in
patchdiag.xref:<br>
<br>
<b>April CPU patchdiag</b> <br clear="all">
119254-80 119254-81<br>
122911-24 122911-25<br>
125215-03 125215-04<br>
141552-03 141552-04<br>
143559-07 143559-08<br>
144488-11 144488-14<br>
<br>
Previously, patdiag.xref would list both the version of the patch that
was in the CPU and the most recent version.<br>
<br>
Guess the question is to Martin or Don: Do you know if this is
intentional?<br>
<br>
-- <br>
Jeff<br>
</blockquote>
<br>
</div></div><div>-- <br>
<a href="http://www.oracle.com/" target="_blank"> <img src="cid:part1.07040907.06060301@oracle.com" name="graphics1" align="bottom" border="0" height="18" width="133"></a> <br>
<font face="Verdana, sans-serif" size="2"><b>Don O'Malley</b></font><br>
<font color="#666666" face="Verdana, sans-serif" size="2"> Manager,
Patch System Test<br>
Revenue Product Engineering | Solaris | Hardware <br>
East Point Business Park, Dublin 3, Ireland<br>
Phone: <a href="tel:%2B353%201%208199764" value="+35318199764" target="_blank">+353 1 8199764</a> <br>
Team Alias: <a href="mailto:rpe_patch_system_test_ww@oracle.com" target="_blank">rpe_patch_system_test_ww@oracle.com</a><br>
</font> </div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>Jeff<br>
</div>