Cannot connect using MyODBC 3.51.12 on Linux

I am trying to get MySQL 4.1.19, MySQL Connector/ODBC 3.51.12, and
iODBC (libiodbc) 3.52.3 to work together on several Linux systems
(e.g., x86 RHAS 4). I cannot get past the following error:

$ iodbctest "DSN=test"
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0305.1107
1: SQLDriverConnect = [MySQL][ODBC 3.51 Driver]Could not determine
the driver name; could not lookup setup library. DSN=(test)
(0) SQLSTATE=HY000
1: ODBC_Connect = [MySQL][ODBC 3.51 Driver]Could not determine the
driver name; could not lookup setup library. DSN=(test)
(0) SQLSTATE=HY000

Have a nice day.

Because the error message ("Could not determine the driver name;
could not lookup setup library.") comes from the MyODBC driver itself
(driver/connect.c:443), I think the problem might be located there.

In sum, I've tried just about everything I can think of to get this
to work. I've checked lots of system configuration details (some
described below), I've tried all sorts of variations in my odbc.ini
file, etc. It looks like it ought to work.

I've seen this error described on the web in a few places, but most
references are to older versions of MyODBC.

I really hope you can help me get unstuck. I'd be happy to work
directly with developers to debug the problem further.

-----------------------------

Here's some background data:

My odbc.ini file:

[test]
Driver = /home/cat/myodbc/lib/libmyodbc3-3.51.12.so
Server = localhost
Port = 49151
User = myuser
Password = mypass
Database = mydb
TraceFile = /home/cat/odbc.trace
Trace = 1

A couple relevant environment variables:

ODBCINI=/home/cat/iodbc/var/odbc.ini
ODBCSYSINI=/home/cat/iodbc/var

I'm fairly certain the correct odbc.ini file is being read, because I
can make changes to it that are reflected by iodbctest.

Here's the myodbc/lib directory contents:

total 400
-rwxr-xr-x 1 root root 22776 Jul 6 15:29 libltdl.so.3*
-rwxr-xr-x 1 root root 181337 Jul 6 15:29 libmyodbc3-3.51.12.so*
-rwxr-xr-x 1 root root 1307 Jul 12 08:36 libmyodbc3.la*
-rwxr-xr-x 1 root root 181417 Jul 6 15:29 libmyodbc3_r-3.51.12.so*
-rwxr-xr-x 1 root root 1331 Jul 12 08:36 libmyodbc3_r.la*
lrwxrwxrwx 1 root root 23 Jul 12 08:36 libmyodbc3_r.so ->
libmyodbc3_r-3.51.12.so*
lrwxrwxrwx 1 root root 21 Jul 12 08:36 libmyodbc3.so ->
libmyodbc3-3.51.12.so*

LD_LIBRARY_PATH includes all the relevant MySQL, MySQL Connector/
ODBC, and iODBC library directories. Running ldd on the libmyodbc
file above shows completely normal and expected results -- no missing
shared objects or anything.

I am able to connect to the MySQL database using the host, port,
user, and password specified in the odbc.ini file, but I don't think
things have progressed that far.

--
Tim Cartwright, Condor Project & VDT
University of Wisconsin-Madison, Computer Science Dept.
1210 West Dayton Street, Room 4265; Madison, WI 53706; USA
Tel: +1 608 262 4002 / Email: cat@cs.wisc.edu

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: Cannot connect using MyODBC 3.51.12 on Linux

Tim,

Please try v3.51.13 at;

ftp.mysql.com/pub/mysql/hidden/connectors

BUT note that we develop against unixODBC except for OSX and MS Windows.

Peter


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: Cannot connect using MyODBC 3.51.12 on Linux

Peter:

Thanks for the quick response!

> Please try v3.51.13 at;
>
> ftp.mysql.com/pub/mysql/hidden/connectors
>
> BUT note that we develop against unixODBC except for OSX and MS
> Windows.

Will 3.51.13 be officially released in the next few days? If not,
then I don't feel comfortable using it in our distribution, which
will be installed at many sites over the next couple months.

I'm going to try reverting to 3.15.06, which apparently has worked
for some people using the particular application that I'm concerned
about (the Globus Toolkit, esp. RLS -- see http://www.globus.org/
toolkit/docs/development/4.2-drafts/data/rls/admin/ for details).
Failing that, I'll probably have to look into switching to unixODBC.

Just so I understand the problem better, what is it that's failing?
What about the ODBC manager we're using (iODBC) could be causing the
problem? Is it not passing data through to your ODBC driver correctly?

--
Tim Cartwright, Condor Project & VDT
University of Wisconsin-Madison, Computer Science Dept.
1210 West Dayton Street, Room 4265; Madison, WI 53706; USA
Tel: +1 608 262 4002 / Email: cat@cs.wisc.edu

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org