Xref: alice comp.databases.oracle.server:83052
Path: alice!news-feed.fnsi.net!news.maxwell.syr.edu!nntp2.deja.com!nnrp1.deja.com!not-for-mail
From: patminnis@my-deja.com
Newsgroups: comp.databases.oracle.server
Subject: Re: UNIX child processes
Date: Wed, 02 Feb 2000 14:44:45 GMT
Organization: Deja.com - Before you buy.
Lines: 55
Message-ID: <879fss$f50$1@nnrp1.deja.com>
References: <877cgr$ugv$1@nnrp1.deja.com> <877och$80m$1@nnrp1.deja.com> <877r6i$a75$1@nnrp1.deja.com> <878f65$o62$1@nnrp1.deja.com>
X-Article-Creation-Date: Wed Feb 02 14:44:45 2000 GMT
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt)
X-Http-Proxy: 1.0 x43.deja.com:80 (Squid/1.1.22) for client 63.64.13.2
X-MyDeja-Info: XMYDJUIDpatminnis

I am reposting my original message with the new information that the
Oracle session in question is not sniped.  I did notice that the parent
pid is 1 which as I recall is normal for a server process.  But this
also means that Oracle must be the one that determines when the process
will be stopped.  SQLNET.EXPIRE_TIME=10 on our system.

Original message follows: (with full test shell script included)

We are running Oracle Applications on a Digital UNIX platform -- but I
have duplicated the effect with simple shell script with sqlplus as
follows:

Shell script written to call sqlplus with PL/SQL block as in:
   sqlplus system/p0l3s <<EOF
   set pages 1000
   set arraysize 1
   whenever oserror exit failure rollback;
   whenever sqlerror exit failure rollback;
   declare
     cursor c1_cursor is
       select a.ACTION_SEQUENCE
         from PAY_PAYROLL_ACTIONS a, PAY_PAYROLL_ACTIONS b;
   begin
     for c1_record in c1_cursor loop
       dbms_output.put_line(c1_record.ACTION_SEQUENCE);
     end loop;
   end;
   /
   EOF
   if [ ! $? ]; then; exit; fi

I find the unix pid that corresponds with the sqlplus and I find the
shell script

I close my telnet session

Shell script process is gone.  sqlplus pid continues running; it is
definitely running -- I can watch the CPU% changing up and down.

This seems to be normal behavior on our system.  Children continue to
run without a parent.

So my question is, why doesn't the child process go away?  Is there a
way to subvert this behavior?  Would I want to?

Oracle Applications DBA's:
This is occurring when we cancel a custom concurrent request.  These
programs are written as host shell scripts which run sqlplus, perhaps
multiple times in the same shell script.




Sent via Deja.com http://www.deja.com/
Before you buy.