Re: script problem solved, but I still don't understand ....

On 14 Oct 2004 16:28:58 -0700, joel-garry_at_home.com (Joel Garry) wrote:

>Ed Stevens <nospam_at_noway.nohow> wrote in message news:<dr5tm0p1v8gf3nt2iarmfege20dt06iepm_at_4ax.com>...
>>
>> And still leaves me with the fundamental question of how I was able to
>> get a good connect -- *not* a 'connected to an idle instance' -- then
>> have the first DML statement result in a ORA-01034: ORACLE not
>> available.
>
>I'm frustrated as heck right now because I've done this same thing and
>can't remember the answer.
>
>But it might be something like being logged on as root rather than the
>oracle user, so you can connect, because that just means running
>sqlplus, but when you try to actually do anything you get the 1034
>because the shared memory area is owned by oracle:dba (or whatever)
>and root is explicitly enjoined from doing certain things in Oracle,
>even if it is in the dba group.
>
>I also have a vague memory of something like this when I forgot the -
>in the su - oracle, where the oracle .profile had the proper
>environment call and the sysadmin had tried to run oracle things as
>root, so the environment was partly set up under cron.
>
>jg

Showing the limits of my unix knowledge ...

So, if a job is submitted by cron, is it being submitted by root or by the user that owns the crontab from which the job was scheduled? I assumed that it was run by the owner of the crontab. In fact I'm pretty certain that if I 'ps -ef | grep oracle' I will see processes that were the result of being scheduled in oracle's crontab.

Are you saying that if I were to log on as root (which I can't do) and $ORACLE_SID were null, I could still issue a 'sqlplus "/ as sysdba" ' and get 'connected' ? If so, and in the case of my original problem, what the heck did sqlplus think it was connected to? Received on Fri Oct 15 2004 - 07:13:49 CDT