[unixODBC-support] RE: unixODBC, OOB, MSSQL and DB2

Matthew Beck matthew.beck at pmigroup.com
Thu Nov 10 09:33:10 GMT 2005

So far I've tried both easysoft and OpenLink drivers on unixODBC, but
they both give me bus errors with this output:

    Incurred fault #5, FLTACCESS  %pc = 0xFFFFFFFF7D156F84
      siginfo: SIGBUS BUS_ADRALN addr=0x10010C744
    Received signal #10, SIGBUS [default]
      siginfo: SIGBUS BUS_ADRALN addr=0x10010C744
        *** process killed ***

Basically, I need a solution that allows my users to utilize both DB2
and SQL drivers.

Fun stuff.  I have 10.5 hours to come up with a solution.  Another
all-nighter for me.


-----Original Message-----
From: unixodbc-support-bounces at easysoft.com
[mailto:unixodbc-support-bounces at easysoft.com] On Behalf Of Nick Gorham
Sent: Thursday, November 10, 2005 1:18 AM
To: Support for the unixODBC project
Subject: Re: [unixODBC-support] unixODBC, OOB, MSSQL

Matthew Beck wrote:

>I'm experiencing some issues with using OOB to connect to MSSQL 2K.
>I also get this same output if I try to connect using a Datadirect SQL

Hang on, you now have a driver manager that expects 4 byte driver 
handles. the 64 bit OOB will be giving 8 byte as will every other driver

other than db2.

If you need both at the same time, the DM code will need much more doing

to it. It would be simpiler if you could have two driver manager tibs. 
It depends on how you are using it.

Nick Gorham
Easysoft Limited
unixODBC-support mailing list
unixODBC-support at easysoft.com

More information about the unixODBC-support mailing list