Re: DBD::SQLAnywhere SEGV when Oracle handle exists

2017-04-12 Thread Douglas Wilson
The issue was the libclntsh that Oracle was loading conflicted with SQLAnywhere , updating Oracle libs and recompiling DBD::Oracle fixes it. On Mar 7, 2017 2:10 PM, "Douglas Wilson" wrote: > That does work, but I can't consider it a practical solution for this. >

Re: DBD::SQLAnywhere SEGV when Oracle handle exists

2017-03-07 Thread Douglas Wilson
That does work, but I can't consider it a practical solution for this. Through print/warns, I've determined it craps out at sacapi->api.sqlany_connect(...), in dbdimp.c, but that's about as far as I can get. I will probably go back to using DBD::Sybase for IQ connections. On Mar 7, 2017 10:11 AM,

Re: DBD::SQLAnywhere SEGV when Oracle handle exists

2017-03-07 Thread Martin J. Evans
On 06-Mar-17 5:38 PM, 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. Try reversing the order in which you connect - if you can. On Mar 4,

Re: DBD::SQLAnywhere SEGV when Oracle handle exists

2017-03-06 Thread Christopher Jones
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: DBD::SQLAnywhere SEGV when Oracle handle exists

2017-03-06 Thread Douglas Wilson
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: >

Re: DBD::SQLAnywhere SEGV when Oracle handle exists

2017-03-04 Thread Martin J. Evans
On 02-Mar-17 10:54 PM, Douglas Wilson wrote: DBD::SQLAnywhere seems to work ok for Sybase IQ, but if I first create a DBD:Oracle handle, the SQLAnywhere connect hangs for a while, and eventually segfaults. FYI on redhat Linux. I don't have the info to hand right now but I've heard similar

Re: DBD::SQLAnywhere SEGV when Oracle handle exists

2017-03-02 Thread Ron Savage
Hi Doug On 03/03/17 09:54, Douglas Wilson wrote: DBD::SQLAnywhere seems to work ok for Sybase IQ, but if I first create a DBD:Oracle handle, the SQLAnywhere connect hangs for a while, and eventually segfaults. FYI on redhat Linux. First thing we ask: What versions of everything are you

DBD::SQLAnywhere SEGV when Oracle handle exists

2017-03-02 Thread Douglas Wilson
DBD::SQLAnywhere seems to work ok for Sybase IQ, but if I first create a DBD:Oracle handle, the SQLAnywhere connect hangs for a while, and eventually segfaults. FYI on redhat Linux.