Alexander, This is the problem for me because I am using PERL as CGI for web applications where the script is querying the data from Oracle database. And if the process is taking too long to return the data to user browser, sometimes, the user will then close the browser or click "STOP" in the browser. In that case, the Oracle process will be staying there forever. This led to the problem of Oracle backup process which is waiting for all processes to complete. Therefore, we need to do a clean up on those orphan processes periodically. But because of all Oracle child processes initiated by PERL are with parent id of 1, the clean up process doesn't know which one is supposed to removed.
Thanks in advance. Alan -----Original Message----- From: Alexander Foken [mailto:[EMAIL PROTECTED] Sent: Friday, September 22, 2006 11:49 AM To: Kong, Alan Cc: [email protected] Subject: Re: Does any one experiencing this problem? Why is that a problem for you? If you are running some kind of Unix, process 1 is init ("the parent of all processes"), new processes with a parent id of 1 are simply new, independant process groups, that do not get killed when the process group with your perl script is killed. (I think this is an isolated transaction-handling process forked by the oracle client library.) man 2 setsid If you are running Windows, ID 1 is NOT special. Alexander On 22.09.2006 17:27, Kong, Alan wrote: > Hi all, > > My system is running an Oracle10G server with PERL DBI, whenever I run > the perl scripts with DBD connect, there will be an Oracle sub-process > with parent ID of 1. Normally, the sub-process should have a parent > ID = pid of the perl script. Running any other scripts with SQL*PLUS > is behaving normal though. > > Does anyone have experience the same problem before? > > Thanks, > Alan > > -- Alexander Foken mailto:[EMAIL PROTECTED] http://www.foken.de/alexander/
