Re: error from opatch installing Apr 2013 PSU

From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Thu, 30 May 2013 07:53:40 -0500
Message-ID: <CAJvnOJZBmbn2ER42vc8hCUoNExDLUDp0kS=50rEEUkfxUrnavg_at_mail.gmail.com>

Yes, orainstall has access to the directory. Thanks for the input though. I once spent several hours tracking down exactly that sort of ownership problem down, until I realized I had unzipped the patch as root rather than Oracle. The highly useful (sarcasm on) error message from opatch was 'patch not applicable'.

On Thu, May 30, 2013 at 7:44 AM, Radoulov, Dimitre <cichomitiko_at_gmail.com>wrote:

> On 30/05/2013 14:39, Andrew Kerber wrote:
>
>> Actually I think the owner of the unzipped patch should be the database
>> instance owner. At least that is what is it always has been in the past.
>>
>
> If I understand correctly, you're installing the latest PSU on GI + DB
> environment in auto mode - opatch auto ... as root.
>
>
> The readme document - Oracle Grid Infrastructure Patch Set Update
> 11.2.0.3.6 (Includes Database PSU 11.2.0.3.6) - 16083653 - states the
> following:
>
> <quote>
> 2.1.4 Download and Unzip the Patch
>
> To apply the patch, it must be accessible from all nodes in the Oracle
> cluster. Download the patch and unzip it to a shared location, this is
> called the <UNZIPPED_PATCH_LOCATION>. This directory must be empty and not
> be /tmp. Additionally, the directory should have read permission for the
> ORA_INSTALL group.
>
> $ cd <UNZIPPED_PATCH_LOCATION>
>
> Check that the directory is empty.
>
> $ ls
>
> Unzip the patch as grid home owner.
>
> $ unzip p16083653_112030_<platform>.**zip
> </quote>
>
> Anyway, I suppose that read permission for the ORA_INSTALL group could be
> sufficient.
> Sorry for the noise, if the above doesn't match your case.
>
>
> Regards
> Dimitre
>

-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'


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

Received on Thu May 30 2013 - 14:53:40 CEST