MySQL driver can't be loaded

[Druid_Elf]

Hi,
I've been browsing the forum but can't seem to find the solution. The problem is as follows. We want to make a datastage (8.0.1) connection to a MySql database.
On the solaris machine we have added the drivers for solaris.
In my .odbc.ini I've made the following entry at the start of the file:
MySqlShop=MySQL ODBC 3.51 Driver DSN
At the end:
[MySqlShop]
Driver=/prd/clb/sft/dts/install/8.0.1/odbc/mysql-connector-odbc-5.1.6-solaris10-sparc-32bit/lib/libmyodbc3S.so
Description=MySQL ODBC 3.51 Driver DSN
SERVER=192.168.245.164
PORT=
USER=******
Password=*****
Database=shop
OPTION=3
SOCKET=
I've also added the entry in uvodbc.config
<MySqlShop>
DBMSTYPE = ODBC
I've also made sure that the driver path is in my LD_LIBRARY_PATH as the first entry.

If i make a job in datastage with the correct connection string I get the following error:
[DataDirect][ODBC Lib] Specified driver could not be loaded
Unable to connect to the database server 'MySqlShop'
DSP.Open GCI $DSP.Open error -100
I am a bit at a loss here. I read in some forums that you have to register with iODBC or unixodbc but we don't use those tools.
Anyone got a thought on what I am doing wrong here ?
Thanks for any help :D

[deps1972]

The Port number is not provided and did you also modified uvodc.config file in project folder?

[Druid_Elf]

Hi,
I filled in the port number but still getting the same error.
Yes I've also modified the uvodbc.config file in my project folder.

Is there any guide on the internet for installing this driver for datastage ?

[chulett]

If there is, it would have to come from the ODBC vendor I would think. That or perhaps you should contact your official support provider and get their help.

[FranklinE]

I'm certainly no expert, but I do notice a difference there from the entries I have for Oracle and MSSQL: the userid and password are set to variables, not what looks like encrypted text.

If what you have is standard practice, then just ignore me.

[Druid_Elf]

Ok some feedback if others should ever have the same problem.
We logged a PMR and the issue got resolved.

Following steps had to be done:
1. Upgrade the branded_odbc drivers with newer driver version from data direct ( version Solaris32-odbc53-091007.tar.z)
2. Add the odbc directory for mysql to LD_Library Path
3. Add a symbolic link for libodbcinst.so in the folder where the mysql driver was present
4. I also needed to use the other lib file that was supplied by mysql
5. Extra entry needed to be added (DriveUnicodeType) in odbc.ini for buffer overflow error (apparently the driver only supports UTF

So in the end my entry looks like this (.odbc.ini):

[MySqlShop]
Driver=/prd/clb/sft/dts/install/8.0.1/odbc/mysql-connector-odbc-5.1.6-solaris10-sparc-32bit/lib/libmyodbc5.so
Description=MySQL ODBC 3.51 Driver DSN
SERVER=192.168.245.164
PORT=3352
USER=*
Password=*
Database=shop
OPTION=3
DriverUnicodeType=1

Connection works fine now

[Sreenivasulu]

Thanks for the update on setting up 'connections' to 'open source db.
It seems setting for ' driver unicode type' is just a 'language setting' and not a restriction due to use of 'open source drivers'

Regards
Sreeni