Re: Critical Update Patch Naming
From: Jared Still <jkstill_at_gmail.com>
Date: Fri, 16 May 2008 10:16:09 -0700
Message-ID: <bf46380805161016q5613d56by6872045c2d047946@mail.gmail.com>
Date: Fri, 16 May 2008 10:16:09 -0700
Message-ID: <bf46380805161016q5613d56by6872045c2d047946@mail.gmail.com>
The result?
Mea Culpa. Oracle changed the CPU to be an all inclusive patch, not just
security,
and changed the naming convention.
Documented? Yes, I just missed it.
Just too much for a DBA to keep up with.
On Tue, May 13, 2008 at 5:55 PM, Jared Still <jkstill_at_gmail.com> wrote:
> A change in how Oracle refers to their patches was the cause of a bit of
> confusion:
>
> http://jkstill.blogspot.com/2008/05/oracles-cpu-patch-naming.html
>
>
> --
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
>
-- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist -- http://www.freelists.org/webpage/oracle-lReceived on Fri May 16 2008 - 12:16:09 CDT