[unixODBC-support] core dump in libodbccr.so on HP iA64
sunf2002 at gmail.com
Tue Nov 13 09:46:53 GMT 2007
I am using unixODBC-2.2.12.
Here's the information in my odbc.ini
I add the UDB39081 in db2 instance as database alias.
If I use the 32bit unixodbc on linux and solaris, when I connect to
db2 on os390 and as400 it will call libodbccr.so samely but no core
dump. And when connect to db2 on NT and Unix libodbccr.so won't be
As I said libodbccr.so won't be called when use unixodbc to load
datadirect driver no matter connect to db2 os390 or as400.
On Nov 13, 2007 5:40 PM, Nick Gorham <nick.gorham at easysoft.com> wrote:
> Cherie Soleil wrote:
> >When we use unixodbc driver manager on HP IA64 we encountered one
> >problem. Would you please help me to have a check.
> >We use unixodbc driver manager to load DB2 driver libdb2o(DB2
> >v220.127.116.11","s070719","U811592","Fixpack 3") to connect to db2. When we
> >connect to db2 on os390 or as400 and do some kinds of cursor operation
> >libodbc.so will call libodbccr.so even we set SQL_CUR_USE_DRIVER and
> >met a core dump in libodbccr.so. ( If connect to db2 on NT or Unix
> >it's ok. If use unixodbc driver manager to connect to datadirect
> >driver libodbccr.so won't be called for all kinds of db2 database.)
> What version of the driver manager are you using? It should never call
> the cursor lib if its set to SQL_CUR_USE_DRIVER.
> Can you send me the ini files you are using?
> It sounds like something very strange is going on.
> Nick Gorham
> Easysoft Limited
> http://www.easysoft.com, http://www.unixODBC.org
> unixODBC-support mailing list
> unixODBC-support at easysoft.com
More information about the unixODBC-support