ODBC, INFORMIX-CLI
Posted in 1999
Topics: Connectivity: ODBC / JDBC / .NET, Server Administration
Hi,
I'm trying to get an UNIX ODBC client to talk to the Informix 7.2 database
running on the same machine (SunOS 5). I got the demo programs supplied in
the cli package to compile, and I set up the environment variables
INFORMIXDIR and LD_LIBRARY_PATH as directed in the documentation. However,
when I run the demo programs, they simply hang there and produce no output
when the function SQLAllocEnv is called. When I interrupt the execution in
a debugger, this is the backtrace I get:
#0 0xef6125e8 in __0FKbosMemLockPUl ()
#1 0xef5e503c in __0fLQeSemaphoreLbosSpinLockv ()
#2 0xef5ff324 in __0FQqeSemaphoreEnterPP6LQeSemaphore ()
#3 0xef7948b4 in __0FJdeleteEnvP6H_DMGENV ()
#4 0xef783310 in SQLAllocEnv ()
I have verified that Informix itself is running correctly (dbaccess works
fine, and a web client (not using ODBC) on the same machine is able to
connect to it okay also)
It seems that I'm doing something really stupid, like not completely
understanding how ODBC is supposed to work. My only previous experience
before with ODBC was with OpenLink, where I got an UNIX client to talk to
SQlServer running on an NT machine, but in that case, I had a requestbroker
running on the NT server. Is there some similar program (driver manager?)
that I have to have running on the Sun machine in my present situation in
order for the ODBC client to talk to the informix database?
Thanks for anyone who can offer some insight into this...
Ken
I figured out (sort of) what the problem was. I was still using my .odbc.ini file from openlink when I tried to run the program with intersolv drivers. when i switched over to the .odbc.ini file that came with the intersolv drivers, the hanging problem went away. It seems kind of weird for the function to hang though, just because of the unexpected format of the .odbc.ini file? (maybe my analysis is completely off, but truss showed the original program to hang right after opening .odbc.ini) k