Re: DBD::SQLAnywhere SEGV when Oracle handle exists

After some searching, I tried using the ora_connect_with_default_signals with INT and CHLD, and tried setting BEQUEATH_DETACH=yes in a local sqlnet.ora, but still same result. On Mar 4, 2017 5:17 AM, "Martin J. Evans" wrote: > On 02-Mar-17 10:54 PM, Douglas Wilson wrote: >

(Fwd) Oracle.pm

- Forwarded message from Gowtham - Date: Mon, 6 Mar 2017 15:40:59 -0600 From: Gowtham To: tim.bu...@pobox.com Subject: Oracle.pm Hi Tim, I feel that you are the right person to check this with. I am trying to understand the

Re: (Fwd) Oracle.pm

Hi Gautam You don't need to examine the source code of Oracle.pm. You need to print out the values of ($dbh,$dbname,$user,$auth,$attr) and focus purely on them, and how they differ from what Oracle.pm expects. On 07/03/17 10:22, Tim Bunce wrote: - Forwarded message from Gowtham

Re: (Fwd) Oracle.pm

Hi Gautam P.S. Do not reply to me directly. Always reply to the DBI Users list. On 07/03/17 11:00, Ron Savage wrote: Hi Gautam You don't need to examine the source code of Oracle.pm. You need to print out the values of ($dbh,$dbname,$user,$auth,$attr) and focus purely on them, and how they

Re: DBD::SQLAnywhere SEGV when Oracle handle exists

On 7/3/17 4:38 am, Douglas Wilson wrote: After some searching, I tried using the ora_connect_with_default_signals with INT and CHLD, and tried setting BEQUEATH_DETACH=yes in a local sqlnet.ora, but still same result. Stack trace? Versions? Have you worked back from the point of the

Re: (Fwd) Oracle.pm

Hi Ron, I did that. I have two scenarios here. Both the scenarios have same ($dbh,$dbname,$user,$auth,$attr) values. Scenario 1: executed code with ORACLE_HOME set to correct value. Scenario 2: executed code with incorrect/wrong ORACLE_HOME env variable. - So my code returns undef in the