Re: Orphaned Unix processes

You can try enabling dead connection detection on the server by adding SQLNET.EXPIRE_TIME=10
in the $TNS_ADMIN/sqlnet.ora. DCD does have a few problems with long running jobs if you are using MTS and I suspect there a few other issues you might encounter.

"Michael" <mloftus_at_wyle.com> wrote in message news:8o1jva$iok$1_at_paxfeed.eni.net...
> I am not sure if this is a server issue, a Unix issue, or an Oracle
> Financials Issue. Our users often ctl-alt-del and terminate their Oracle
> Financials Session because it appears to "hang". It really isn't, but
 their
> misuse of the system causes table scans, etc, so they just kill their
 client
> application (10.7) rather than wait.
>
> The database continues to chug along on their process. Eventually, the
> process detects the missing user connection and terminates but sometimes
> there is an orphaned Unix parent process that spins at 40 - 75% of CPU
 that
> does not go away until I kill it. This is really a bother, as the users
> blame the DBA's for the "problem". We are supposed to have some easy and
> painless solution!
>
> Is there some way to deal with this in an automated fashion? A script
 that
> can detect these orphans and kill them automatically?
>
> Thanks
>
> Michael Loftus
> Wyle Electronics
>
>
>
>
Received on Wed Aug 23 2000 - 18:38:40 CDT