ODBC error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
ketanshah123
Participant
Posts: 88
Joined: Wed Apr 05, 2006 1:04 am

ODBC error

Post by ketanshah123 »

Hi all

While trying to importing table definition using ODBC table defintion option
I am getting following error. whats this error? How to resolve it?

we have set up new development server on that only getting the error .

Error message :

DSR.MetaGeta(GET.TABLES)(SQLTables): BCI Error: SQLSTATE=S1000,CODE=1248,[DataStage][SQL Client][ODBC][DataDirect][ODBC DB2 Wire Protocol driver]Unhandled CodePoint: 35


thanx in advance
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

This error is being generated by the driver. You should contact Data Direct (the supplier of the driver).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

do you see any thing like 'QEWSD=38843' in you .odbc.ini file?
arnabdey
Participant
Posts: 50
Joined: Wed Jan 10, 2007 5:56 am

Post by arnabdey »

Hi

Check whether you have set up the .odbc.ini (in Engine folder) and uvodbc.config file (in the Projects folder). The uvodbc file should mention the data source names and the .odbc.ini file should contain connectivity details like ip address, database driver etc

Thanks
Arnab
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Note: if your DataStage server is on Windows, then you will not have a .odbc.ini file - instead, ODBC.INI is a Registry entry. It is maintained using the ODBC Administrator (odbcad32.exe) on the DataStage server machine.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply