Re: (Fwd) Bug in Oracle 11g2 with DBD::Oracle
"Martin J. Evans" <[email protected]>
| Newsgroups | gmane.comp.lang.perl.modules.dbi.general |
|---|---|
| Organization | Easysoft Limited |
| Message-ID | <[email protected]> |
On 05/03/13 12:14, Charles Jardine wrote: > On 05/03/13 10:08, [email protected] wrote: >> ----- Forwarded message from Mahdi Sbeih <[email protected]> ----- >> >> Date: Tue, 5 Mar 2013 00:45:26 -0800 >> From: Mahdi Sbeih <[email protected]> >> To: "[email protected]" <[email protected]> >> Subject: Bug in Oracle 11g2 with DBD::Oracle >> >> Dear Tim, >> >> Sorry for sending this email directly to you, but I am not an active >> member in Perl lists and forums and maybe you can direct this email >> to whom is responsible for the development of Perl DBD::Oracle >> module. >> >> I found a bug related to the ora_connect_with_default_signals >> feature. >> >> On our system RHEL5 Oracle11gR2, we had to use this feature on the >> child signal in order to avoid the "-1" return from the system call >> ora_connect_with_default_signals => ['CHLD'] > > The best way to deal with the -1 return from system() is to add > > bequeath_detach = yes Agreed. > to your client-side sqlnet.ora file. If you do this you will not > need to use ora_connect_with_default_signals. > >> This caused a sever bug, if the Perl script is running in the >> background and doesn't exit, every time it connects to the oracle >> database server it will create a zombie process, and this will later >> crash the machine itself since it will consume all the processes on >> the machine. > > I think that ora_connect_with_default_signals is misguided. > As it happens so do I when it comes to SIGCHLD. However, some Oracle client libraries also trap SIGINT and SIGQUIT where I have more of a problem. Perhaps I'll find some time to update the pod. Martin -- Martin J. Evans Easysoft Limited http://www.easysoft.com