Hi Martin,

I followed up with the team that generates patchdiag on Friday.

There was a recent code change to better handle EOL patches that triggered the issue you reported on Friday.

All should be fixed now.

Best,
-Don

On 03/10/11 08:12, Martin Paul wrote:
Don O'Malley wrote:
That said, something has happened to trigger 119081-25 being marked as obsolete (I suspect this is a result of an internal process).

In the current patchdiag.xref (Oct/02/11) the state of 119081-25 has been reverted to active (not obsolete) again. Same for the other 7 patches that were affected (106922, 108982, 109082, 109647, 117662, 117851, 119070). So everything is fine again.

I also checked for other possible problematic patches with this command:

  grep '|O|' patchdiag.xref | egrep -vi "Obsoleted by|withdrawn"

It only comes up with 4 old revisions of 118822 now, which are marked Obsolete and Bad, which is not a problem.

If you ever find an explanation for how this happened, I'd be interested to hear about it!

Martin.


--

Don O'Malley
Manager,Patch System Test
Revenue Product Engineering | Solaris | Hardware
East Point Business Park, Dublin 3, Ireland
Phone: +353 1 8199764
Team Alias: rpe_patch_system_test...@oracle.com

Reply via email to