Page 1 of 1

Adding unix odbc file in DSEngine odbc.ini file.

Posted: Thu Oct 02, 2014 10:06 am
by AmeyJoshi14
Hi Experts,

We are facing some issues with build-in data direct drivers for Microsoft SQl server in our Linux server. Due to this we have installed 'Microsoft ODBC Driver 11 for SQL Server on Linux' in our linux servers. I have added this driver file in odbc.ini file in $DSENV, but when I am trying to test connection it is failing with error message as 'Unicode converter buffer overflow'.

Can we use external drivers(other than Data Direct) in Datastage? Do we have to restart DSEngine if we have modified(added linux driver path) LDS_LIBRARY_PATH ? :roll:

Below is the sample odbc file :

Code: Select all

[DBNAME_UNixDriver]
Driver=/opt/microsoft/msodbcsql/lib64/libmsodbcsql-11.0.so.2270.0
Description=Microsoft ODBC Driver 11 for SQL Server
Database=DBNAME
LogonID=uid
Password=pwd
Address=ServerName
QuotedId=No
AnsiNPW=No

---Tried with default sample of microsofrt drivers

[DSNname]
Driver=SQL Server Native Client 11.0
Description=My Sample ODBC Database Connection
Trace=Yes
Server=[server address]
Port=1433
Database=NSCDB_3
Microsoft ODBC driver:-
http://msdn.microsoft.com/en-us/library ... .110).aspx

Thanks in Advance!!

Posted: Thu Oct 02, 2014 10:31 am
by PaulVL
For your orriginal odbc entry with the standard branded odbc drivers, did you follow step 1 from this link:


http://www-01.ibm.com/support/docview.w ... wg21580747

Posted: Thu Oct 02, 2014 2:08 pm
by AmeyJoshi14
Thanks Paul!!
When I added the 'DriverUnicodeType=1 ' it worked!!! :D

Now the problem is for some of the columns it is adding '?' at end :roll: :roll:

Posted: Thu Oct 02, 2014 3:08 pm
by PaulVL
Are you sure it's a ? or are you using a viewer that does not support the character set you are using.