Re: Identify CPU/PSU patch
- From: Jack van Zanen <jack@xxxxxxxxxxxx>
- To: oratune@xxxxxxxxx
- Date: Fri, 2 Sep 2011 08:58:45 +1000
That is correct only from oracle 11G (R2 I believe). Older versions
definately did not populate.
Jack van Zanen
-------------------------
This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient. If you are not the intended recipient,
please be aware that any disclosure, copying, distribution or use of this
e-mail or any attachment is prohibited. If you have received this e-mail in
error, please contact the sender and delete all copies.
Thank you for your cooperation
On Fri, Sep 2, 2011 at 4:55 AM, David Fitzjarrell <oratune@xxxxxxxxx> wrote:
> They are populated as I installed and patched an 11.2.0.2 home then created
> a database and the PSU information is reported.
>
> David Fitzjarrell
>
>
> From: Frits Hoogland <frits.hoogland@xxxxxxxxx>
> To: "oratune@xxxxxxxxx" <oratune@xxxxxxxxx>
> Cc: "pete@xxxxxxxxxxxxxxxx" <pete@xxxxxxxxxxxxxxxx>; "smishra_97@xxxxxxxxx"
> <smishra_97@xxxxxxxxx>; "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
> Sent: Thursday, September 1, 2011 11:47 AM
> Subject: Re: Identify CPU/PSU patch
>
> Please mind database views like DBA_REGISTRY_HISTORY are not filled
> when databases are created after the CPU/psu patches are applied to
> the oracle home, AFAIK. Or when the database part of the patch is
> forgotten.
>
> So, the most reliable way is to use the opatch information.
>
> I encountered above situation when auditing exadata db's (fairly new
> db's), and I assume psu/CPU patches work the same way.
>
> Frits Hoogland
> Principal Consultant
>
> VX Company IT Services B.V.
> T +31 6 5356 9942
> F +31 35 539 0908
> E fhoogland@xxxxxxxxxxxxx
> I http://www.vxcompany.com
>
> (Sent from my iPhone, typo's are expected)
>
>
> Op 1 sep. 2011 om 20:17 heeft David Fitzjarrell <oratune@xxxxxxxxx>
> het volgende geschreven:
>
> > Thanks, Pete, I was searching for my script that populated a reporting
> table with that information and found another using registry$history.
> Looking further into the mountain of scripts I have I finally found it, and
> you are correct.
> >
> > David Fitzjarrell
> >
> >
> > From: Pete Finnigan <pete@xxxxxxxxxxxxxxxx>
> > To: smishra_97@xxxxxxxxx
> > Cc: David Fitzjarrell <oratune@xxxxxxxxx>; "oracle-l@xxxxxxxxxxxxx" <
> oracle-l@xxxxxxxxxxxxx>
> > Sent: Thursday, September 1, 2011 11:09 AM
> > Subject: Re: Identify CPU/PSU patch
> >
> > Both,
> >
> > DBA_REGISTRY_HISTORY is the proper interface..:-)
> >
> > cheers
> >
> > Pete
> >
> > Sanjay Mishra wrote:
> >> Thanks David
> >>
> >>
> >>
> >> ________________________________
> >> From: David Fitzjarrell <oratune@xxxxxxxxx>
> >> To: "smishra_97@xxxxxxxxx" <smishra_97@xxxxxxxxx>; "
> oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
> >> Sent: Wednesday, August 31, 2011 12:48 PM
> >> Subject: Re: Identify CPU/PSU patch
> >>
> >>
> >> Query REGISTRY$HISTORY for CPU/PSU information for an instance.
> >>
> >>
> >> David Fitzjarrell
> >>
> >>
> >> From: Sanjay Mishra <smishra_97@xxxxxxxxx>
> >> To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
> >> Sent: Wednesday, August 31, 2011 9:09 AM
> >> Subject: Identify CPU/PSU patch
> >>
> >>
> >> Hi
> >>
> >>
> >> Does anyone know what is best way to identify as what CPU/PSU patch is
> applied to the existing Oracle Software. We have 100's of database servers
> and some new are added on regular basis. In order to make sure that new
> database got the CPU or PSU Patch applied and so what is best way to get
> this details.
> >>
> >>
> >> One way is to get this from Opatch and then take the latest patch number
> and search with metalink to get idea if this is part of which CPU.PSU patch.
> This is surely cumbersome or not efficient approach. Also cannot use
> existing database with existing software as it might be missed to apply the
> patch in the database.
> >>
> >> TIA
> >> Sanjay
> >
> > --
> >
> > Pete Finnigan
> > CEO and Founder
> > PeteFinnigan.com Limited
> >
> > Specialists in database security.
> >
> > Makers of PFCLScan the database security auditing tool.
> > Makers of PFCLObfuscate the tool to protect IPR in your PL/SQL
> >
> > If you need help to audit or secure an Oracle database, please ask for
> > details of our training courses and consulting services
> >
> > Phone: +44 (0)1904 791188
> > Fax : +44 (0)1904 791188
> > Mob : +44 (0)7759 277220
> > email: pete@xxxxxxxxxxxxxxxx
> > site : http://www.petefinnigan.com
> >
> > Registered Office: 9 Beech Grove, Acomb, York, YO26 5LD, United Kingdom
> > Company No : 4664901
> > VAT No. : 940668114
> >
> > Please note that this email communication is intended only for the
> > addressee and may contain confidential or privileged information. The
> > contents of this email may be circulated internally within your
> > organisation only and may not be communicated to third parties without
> > the prior written permission of PeteFinnigan.com Limited. This email is
> > not intended nor should it be taken to create any legal relations,
> > contractual or otherwise.
> > --
> > //www.freelists.org/webpage/oracle-l
> >
> >
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
