Db2-ODBC Connectivity Issue (AIX 5.3)

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
rv_kumar
Participant
Posts: 10
Joined: Thu Jun 22, 2006 1:21 pm

Db2-ODBC Connectivity Issue (AIX 5.3)

Post by rv_kumar »

Hi,

I'm trying to setup the ODBC connectivity to DB2 database by adding the following DSN details at .odbc.ini file.

[DB2_SEMATST]
Driver=/fs2/IBM/InformationServer/Server/branded_odbc/lib/VMdb222.so
Description=DataDirect DB2 Wire Protocol Driver
AddStringToCreateTable=
AlternateID=
DynamicSections=100
GrantAuthid=PUBLIC
GrantExecute=1
IpAddress=11.16.154.52
IsolationLevel=CURSOR_STABILITY
Location=SEMATST
LogonID=idmusr
Password=idmusr
Package=db2inst1
PackageOwner=
TcpPort=50000
WithHold=1

Also updated the uvodbc.config file at the project level with the following entries:

[ODBC DATA SOURCES]
<localuv>
DBMSTYPE = UNIVERSE
network = TCP/IP
service = uvserver
host = 127.0.0.1
<ORA_EPIMRKT>
DBMSTYPE = ODBC
<DB2_SEMSTST>
DBMSTYPE = ODBC

While trying to import the table definitions through ODBC I'm getting the following error.

DSR.MetaGeta(GET.DSNINFO)(SQLConnect('DB2_SEMSTST','idmusr')): BCI Error:
SQLSTATE=IM002,CODE=0,[DataStage][SQL Client][ODBC][DataDirect][ODBC lib] Data source name not found and no default driver specified

Any help would be appreciated.

Thanks
Vijay R
Thanks
Vijay R
WDWolf
Charter Member
Charter Member
Posts: 14
Joined: Mon Dec 05, 2005 12:06 pm

Post by WDWolf »

add a blank line after each entry in the project level odbc...I know it sounds weird...and also spell it the same [DB2_SEMATST] and <DB2_SEMSTST>
William Wolf
Wolf Consulting
612-719-9066
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The names are spelled differently in the two files. Is it DB2_SEMATST or DB2_SEMSTST ?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
rv_kumar
Participant
Posts: 10
Joined: Thu Jun 22, 2006 1:21 pm

Post by rv_kumar »

Thanks to everyone. As pointed out it was typo on DSN names between the .odbc.ini and uvodbc.config files.
Thanks
Vijay R
Post Reply