Re: Identify CPU/PSU patch

  • From: Sanjay Mishra <smishra_97@xxxxxxxxx>
  • To: D'Hooge Freek <Freek.DHooge@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 31 Aug 2011 12:27:28 -0700 (PDT)

Thanks Freek.



________________________________
From: D'Hooge Freek <Freek.DHooge@xxxxxxxxx>
To: "smishra_97@xxxxxxxxx" <smishra_97@xxxxxxxxx>; "oracle-l@xxxxxxxxxxxxx" 
<oracle-l@xxxxxxxxxxxxx>
Sent: Wednesday, August 31, 2011 12:36 PM
Subject: RE: Identify CPU/PSU patch

PSU patches can easily be identified with opatch lsinventy -bugs_fixed:

[xxxx@xxxxx ~]$ opatch lsinventory -bugs_fixed | grep PSU
10248523   11724916  Tue May 17 16:08:01 CEST 2011  DATABASE PSU 11.2.0.2.1
11724916   11724916  Tue May 17 16:08:01 CEST 2011  DATABASE PSU 11.2.0.2.2 
(INCLUDES CPUAPR2011)
12311357   12311357  Tue May 17 16:07:34 CEST 2011  GI PSU 11.2.0.2.2 (INCLUDES 
DATABASE PSU 11.2.0.2.

In principle you can do the same with CPU, but the number of false positives 
will be mutch higher.

Regards,

Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
---
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Sanjay Mishra
Sent: woensdag 31 augustus 2011 18:09
To: oracle-l@xxxxxxxxxxxxx
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

Other related posts: