Re: oerr problem in oracle 12c.

On Tuesday, February 4, 2014 1:29:07 PM UTC-8, Mark D Powell wrote:
> On Tuesday, February 4, 2014 2:48:17 PM UTC-5, Frank Langelage wrote:
>
> > Similar but not exactly equal on Solaris SPARC 10:
>
> >
>
> > oerr ora 257
>
> >
>
> > /opt/oracle/product/o12cR1/bin/oerr:
>
> >
>
> > /opt/oracle/product/o12cR1/perl/bin/perl: cannot execute
>
> >
>
> > Directory rights are fine:
>
> >
>
> > ls -l /opt/oracle/product/o12cR1/perl
>
> >
>
> > total 6
>
> >
>
> > drwxr-xr-x 2 oracle dba 1024 Jun 26 2013 bin
>
> >
>
> > drwxr-xr-x 4 oracle dba 512 Jun 26 2013 lib
>
> >
>
> > drwxr-xr-x 4 oracle dba 512 Jun 26 2013 man
>
> >
>
> >
>
> > But permissions of files within those dirs are not, e.g.
>
> >
>
> > ls -l /opt/oracle/product/o12cR1/perl/bin/perl
>
> >
>
> > -rwx------ 1 oracle dba 2730784 Dec 19 2011
>
> >
>
> > /opt/oracle/product/o12cR1/perl/bin/perl
>
> >
>
> > On 04.02.14 16:38, Mladen Gogala wrote:
>
> >
>
> > > I tried to do oerr from a non-oracle account, with the following result:
>
> >
>
> > >
>
> >
>
> > > oerr ora 257
>
> >
>
> > > Can't locate English.pm in _at_INC (@INC contains: /oracle/product/12.1.0.1/
>
> >
>
> > > dbhome1/perl/lib/site_perl/5.14.1/x86_64-linux-thread-multi /oracle/
>
> >
>
> > > product/12.1.0.1/dbhome1/perl/lib/site_perl/5.14.1 /oracle/
>
> >
>
> > > product/12.1.0.1/dbhome1/perl/lib/5.14.1/x86_64-linux-thread-multi /
>
> >
>
> > > oracle/product/12.1.0.1/dbhome1/perl/lib/5.14.1 .)
>
> >
>
> > >
>
> >
>
> > > The solution is very simple, as expected:
>
> >
>
> > >
>
> >
>
> > > chmod -R 750 /oracle/product/12.1.0.1/dbhome1/perl
>
> >
>
> > >
>
> >
>
> > > The user that I was using is a member of the oinstall group:
>
> >
>
> > >
>
> >
>
> > > mgogala_at_medo ~]$ id
>
> >
>
> > > uid=1000(mgogala) gid=1000(mgogala) groups=1000(mgogala),10(wheel),39
>
> >
>
> > > (video),987(vboxusers),1001(oinstall)
>
>
>
> Thank you both for the information. It would seem Oracle has been messing up the file permissions since 10g. At least Oracle is consistent. 8-D
>

Rilly. Everyone is so concerned about rpc's or whatever sitting out there since the last century, ( http://www.securityfocus.com/bid/64856/discuss ) while poor jr. DBA's are setting everything to 777 to try to make it all work.

jg

-- 
_at_home.com is bogus.
http://www.thewire.com/entertainment/2014/01/jeopardys-newest-star-proves-optimal-strategy-really-unfriendly/357609/