Does any one experiencing this problem?

------_=_NextPart_001_01C6DE5B.97638FB4
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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
=3D 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

------_=_NextPart_001_01C6DE5B.97638FB4--

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:alexander@foken.de http://www.foken.de/alexander/

RE: Does any one experiencing this problem?

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:alexander@foken.de]=20
Sent: Friday, September 22, 2006 11:49 AM
To: Kong, Alan
Cc: dbi-users@perl.org
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=20
> ID =3D pid of the perl script. Running any other scripts with =
SQL*PLUS=20
> is behaving normal though.
>
> Does anyone have experience the same problem before?
>
> Thanks,
> Alan
>
> =20


--
Alexander Foken
mailto:alexander@foken.de http://www.foken.de/alexander/

RE: Does any one experiencing this problem?

This is not a DBI issue. In Oracle, orphaned processes are harvested by
the SMON process. Your DBA should know this and be able to act
accordingly by setting SQL*Net parameters on the server and waking up
the SMON process to harvest the orphans.

--
Ron Reidy
Lead DBA
Array BioPharma, Inc.

-----Original Message-----
From: Kong, Alan [mailto:KongA@coned.com]=20
Sent: Friday, September 22, 2006 10:09 AM
To: Alexander Foken
Cc: dbi-users@perl.org
Subject: RE: Does any one experiencing this problem?

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:alexander@foken.de]=20
Sent: Friday, September 22, 2006 11:49 AM
To: Kong, Alan
Cc: dbi-users@perl.org
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=20
> ID =3D pid of the perl script. Running any other scripts with =
SQL*PLUS=20
> is behaving normal though.
>
> Does anyone have experience the same problem before?
>
> Thanks,
> Alan
>
> =20


--
Alexander Foken
mailto:alexander@foken.de http://www.foken.de/alexander/


This electronic message transmission is a PRIVATE communication which =
contains
information which may be confidential or privileged. The information is =
intended=20
to be for the use of the individual or entity named above. If you are =
not the=20
intended recipient, please be aware that any disclosure, copying, =
distribution=20
or use of the contents of this information is prohibited. Please notify =
the
sender of the delivery error by replying to this message, or notify us =
by
telephone (877-633-2436, ext. 0), and then delete it from your system.

RE: Does any one experiencing this problem?

Thanks for your direction, Ron.=20

-----Original Message-----
From: Reidy, Ron [mailto:Ron.Reidy@arraybiopharma.com]=20
Sent: Friday, September 22, 2006 1:05 PM
To: Kong, Alan; Alexander Foken
Cc: dbi-users@perl.org
Subject: RE: Does any one experiencing this problem?

This is not a DBI issue. In Oracle, orphaned processes are harvested by
the SMON process. Your DBA should know this and be able to act
accordingly by setting SQL*Net parameters on the server and waking up
the SMON process to harvest the orphans.

--
Ron Reidy
Lead DBA
Array BioPharma, Inc.

-----Original Message-----
From: Kong, Alan [mailto:KongA@coned.com]
Sent: Friday, September 22, 2006 10:09 AM
To: Alexander Foken
Cc: dbi-users@perl.org
Subject: RE: Does any one experiencing this problem?

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:alexander@foken.de]
Sent: Friday, September 22, 2006 11:49 AM
To: Kong, Alan
Cc: dbi-users@perl.org
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=20
> ID =3D pid of the perl script. Running any other scripts with =
SQL*PLUS=20
> is behaving normal though.
>
> Does anyone have experience the same problem before?
>
> Thanks,
> Alan
>
> =20


--
Alexander Foken
mailto:alexander@foken.de http://www.foken.de/alexander/


This electronic message transmission is a PRIVATE communication which
contains information which may be confidential or privileged. The
information is intended to be for the use of the individual or entity
named above. If you are not the intended recipient, please be aware that
any disclosure, copying, distribution or use of the contents of this
information is prohibited. Please notify the sender of the delivery
error by replying to this message, or notify us by telephone
(877-633-2436, ext. 0), and then delete it from your system.