Re: NOT OWNER
Posted in 1999
Topics: Stored Procedures & SPL, Platform-Specific Issues
On Tue, 28 Sep 1999 14:40:52 -0500, "Rick Fahey" <r.fahey@usa.net>
wrote:
>Hi All,
>
>I have a problem with executing both a stored procedure and setting the
>debug trace.
>I'm running 7.24 uc7 on AIX 4.1.5.
>If I execute a stored procedure that issues the SYSTEM command, I get the
>following error.
>
>668: System command cannot be executed.> 1: Not owner
>
>OR
>
>If I execute an SQL to set debug trace to 'somethingfile', I get the error,
>
>648: cannot open debug file for stored procedure
>1: Not Owner
>
> In both cases, I can set the file to be in any directory, put 777 on
>permissions and own the directory/file.
>This has no different result. I believe Informix is not even going as far as
>to actually check the directory because,
>If I remove it all together, I still get the same error! BUT, If I run it as
>user Informix it all works fine. Also, as
>user Informix, if I remove the directory/file, I get a n error indicating
>it does not exist. Which indicates, that Informix
>is getting messed up, before he actually check for the file, when the SQL is
>run by a User other than Informix.
>
>Any help would be appreciated.
Hi Rick,
It's a long time since I came across this problem (it's a long time
time since I did any development!!), but I found these error messages
to be very misleading. I too messed around with permissions for a
while before I discovered the problems were due to environment
settings. SPL system commands run in a very basic environment by
default - your command is probably simply not being found. I got
around it by specifying full paths to commands, and in some cases
creating shell scripts to be run by the system command which started
by setting the environment required.
HTH,
Richard.
I too run into this problem.. My work around was same as Rick Tohomas indicated..
However 2 more things to add:
1. Your SPL, did it get executed by cron job..
2. Does this SYSTEM calls another script(ksh, csh, perl) other than born
shell?
If condition 1 and 2, you have to make sure in your scripts(item 2) contains
informix environment variable set(including $INFORMIXDIR/bin)
If not 1. you make sure your full path is explicity specified in SYSTEM or
.profile
2. applies for all cases..
Richard Thomas wrote:
> On Tue, 28 Sep 1999 14:40:52 -0500, "Rick Fahey" <r.fahey@usa.net>
> wrote:
>
> >Hi All,
> >
> >I have a problem with executing both a stored procedure and setting the
> >debug trace.
> >I'm running 7.24 uc7 on AIX 4.1.5.
> >If I execute a stored procedure that issues the SYSTEM command, I get the
> >following error.
> >
> >668: System command cannot be executed.> > 1: Not owner
> >
> >OR
> >
> >If I execute an SQL to set debug trace to 'somethingfile', I get the error,
> >
> >648: cannot open debug file for stored procedure
> >1: Not Owner
> >
> > In both cases, I can set the file to be in any directory, put 777 on
> >permissions and own the directory/file.
> >This has no different result. I believe Informix is not even going as far as
> >to actually check the directory because,
> >If I remove it all together, I still get the same error! BUT, If I run it as
> >user Informix it all works fine. Also, as
> >user Informix, if I remove the directory/file, I get a n error indicating
> >it does not exist. Which indicates, that Informix
> >is getting messed up, before he actually check for the file, when the SQL is
> >run by a User other than Informix.
> >
> >Any help would be appreciated.
>
> Hi Rick,
>
> It's a long time since I came across this problem (it's a long time
> time since I did any development!!), but I found these error messages
> to be very misleading. I too messed around with permissions for a
> while before I discovered the problems were due to environment
> settings. SPL system commands run in a very basic environment by
> default - your command is probably simply not being found. I got
> around it by specifying full paths to commands, and in some cases
> creating shell scripts to be run by the system command which started
> by setting the environment required.
>
> HTH,
>
> Richard.
On Wed, 29 Sep 1999 18:58:28 GMT, Kevin Kim <Kevin.K.Kim@pop.mcit.com> wrote: >This is a multi-part message in MIME format. >--------------7F59AB88094132C44FBFE3CF >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >I too run into this problem.. My work around was same as Rick Tohomas indicated.. How did you find out my stage name ? ;-)