Bug 134839 - ODBC/mysql library symbol error
ODBC/mysql library symbol error
Status: CLOSED DUPLICATE of bug 122877
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: unixODBC (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Lane
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-10-06 13:41 EDT by Alexandre Oliva
Modified: 2013-07-02 23:02 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:06:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexandre Oliva 2004-10-06 13:41:46 EDT
AMD64 distribution produces unresolved symbol error when attempting to
use libmyodbc.so driver.

1. Install mysql-server, start mysqld service
2. Install ODBC packages
3. Configure odbc.ini / odbcinst.ini as follows:

% cat /etc/odbc.ini
% cat /etc/odbcinst.ini
# Example driver definitinions

# Included in the unixODBC package
#Description     = ODBC for PostgreSQL
#Driver          = /usr/lib/libodbcpsql.so
#Setup           = /usr/lib/libodbcpsqlS.so
#FileUsage       = 1

# Driver from the MyODBC package
# Setup from the unixODBC package
Description    = ODBC for MySQL
Driver         = /usr/lib64/libmyodbc.so
Setup          = /usr/lib64/libodbcmyS.so
FileUsage      = 1

4. isql -v MySQL-test test
[unixODBC][Driver Manager]Can't open lib '/usr/lib64/libmyodbc.so' :
/usr/lib64/libmyodbc.so: undefined symbol: _dig_vec
[ISQL]ERROR: Could not SQLConnect

_dig_vec is provided by /usr/lib64/mysql/libmysqlclient.so.10.  If I
had to guess, I'd say this problem has to do with incorrect settings
of library search paths (lib x lib64).

I have a strong suspicion on unixODBC.  It doesn't seem to be
lib64-compatible.  Not only does the default .ini file mention
/usr/lib, that's unlikely to work on a lib64 box, but also:

% strings /usr/lib64/libodbc.so.1 | grep /lib

The occurrences of /lib:/usr/lib feel like a strong indication that it
might fail to locate libraries.  A similar configuration (with
s/lib64/lib/g) works on an ia32 box.
Comment 2 Tom Lane 2004-10-06 15:08:08 EDT
I think this is the same issue as bug #122877.  Not sure yet whether
it is MyODBC or unixODBC's fault, though your idea about search path
seems plausible.
Comment 3 Alexandre Oliva 2004-10-06 18:00:11 EDT

*** This bug has been marked as a duplicate of 122877 ***
Comment 4 Tom Lane 2004-11-11 15:51:29 EST
Turns out the bug is really in MyODBC.  I'm not sure what those
strings in libodbc are being used for, if anything at all, but the
real problem was mislinkage of libmyodbc.so against its required

I'm going to leave this bug classified as unixODBC anyway, because it
might help lead people to the right thing if they assume it's a
unixODBC problem.
Comment 5 Red Hat Bugzilla 2006-02-21 14:06:10 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.