RE: version including the PSU patch level

From: Terrian, Thomas J Mr CTR DLA J6DIB <Tom.Terrian.ctr_at_dla.mil>
Date: Wed, 27 Oct 2010 07:38:05 -0400
Message-ID: <96FC82DA2FD4354D9A8B8434B6E7003D42F7F6_at_COL0SGEM20.AD.DLA.MIL>

Thanks for all of the responses. Here is the solution as I see it:

Software:

        opatch lsinventory -bugs_fixed | grep PSU | sort Database:

	column comments format a30;
	select to_char(ACTION_TIME,'DD-MON-YY') action_date, COMMENTS 
	from registry$history 
	order by action_time;

Thanks again,
Tom

-----Original Message-----

From: Terrian, Thomas J Mr CTR DLA J6DIB Sent: Tuesday, October 26, 2010 3:27 PM
To: 'lyallbarbour_at_sanfranmail.com'; oracle-l_at_freelists.org Subject: RE: version including the PSU patch level

Is there any way to do this for an ASM instance...since it doesn't have datafiles and all? Any v$ view perhaps?

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of lyallbarbour_at_sanfranmail.com Sent: Tuesday, October 26, 2010 2:41 PM
To: oracle-l_at_freelists.org
Subject: Re: version including the PSU patch level

Check dba_registry_history

-----Original Message-----

From: Terrian, Thomas J Mr CTR DLA J6DIB <Tom.Terrian.ctr_at_dla.mil> To: oracle-l_at_freelists.org
Sent: Tue, Oct 26, 2010 2:18 pm
Subject: version including the PSU patch level

Does anyone know how to determine the patch level of a database including

the PSU level. v$version shows 10.2.0.4.0 but I know we applied the PSU

10.2.0.4.4....

(I would rather not run opatch lsinventory and then look up the patch

number)

Thanks,

Tom

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Oct 27 2010 - 06:38:05 CDT