Page 1 of 1
unix connection error
Posted: Tue Nov 18, 2003 1:57 am
by sharad
hi
ive installed 5.1 on a solaris box ,set up my .profile,dsenv,.odbc.ini,uvodbc.config and yet when trying to import table definitions i get this error DSR.MetaGeta(GET.TABLES)(SQLConnect('MedClearODBC','dsadm')): BCI Error:
SQLSTATE=IM002,CODE=0,[DataStage][SQL Client][ODBC][MERANT][ODBC lib] Data source name not found and no default driver specified
what could be the problem
Posted: Tue Nov 18, 2003 7:02 am
by 1stpoint
Keep in mind that on unix things are case-sensitive.
Ensure that your uvodbc.config and odbc.ini are correct. Also check the permissions on these files (I believe ascential recommended 744 at one point but they are not executables so they can be 644).
[/quote]
Posted: Tue Nov 18, 2003 7:40 am
by mhester
If you have not defined ODBC connections in the uvodbc.config and .odbc.ini files then you should search this forum for either of those two words and you will find your answer.
Regards,
Michael Hester
Posted: Tue Nov 18, 2003 9:34 am
by lateshj
I had got a similar error, and reason could be
1. MedClearODBC does not exists in the .odbc.ini file
pls check the name, case...
Latesh
Posted: Wed Nov 19, 2003 3:09 am
by sharad
there was a previous installation that worked but was later deleted i restored the backups of the .odbc.ini ,n other files n they are exactly the same only diff is that we using solaris 2.9 (does DS 5.2 work on solaris 2.9)
,and where would i be able to get a 32 driver for informix the current 1 in using is VMinf18.so
Posted: Wed Nov 19, 2003 4:21 am
by Paul Preston
On Solaris platform there is a master uvodbc.config file in the datastage home directory and there are also project level copies in each project directory.
Make sure the correct uvodbc.config is gettign picked up.
Also double check that the dirver specified really does exist and is readable.
Paul Preston
Posted: Wed Nov 19, 2003 5:17 am
by sharad
[does DS 5.2 work on solaris 2.9
Posted: Wed Nov 19, 2003 6:38 am
by mhester
Make sure the correct uvodbc.config is gettign picked up.
The uvodbc.config file in the home directory is the master. If you have values in the project level uvodbc.config files then these will override what is in the home dir. This allows you to make project level DSN's available.
Regards,
Michael Hester
Posted: Wed Nov 19, 2003 6:42 am
by mhester
does DS 5.2 work on solaris 2.9
Straight from the Ascential website.
DataStage XE for Solaris
Release OS Release
7.0 Solaris 2.7 & 2.8 & 2.9
6.0.1 Solaris 2.7 & 2.8
6.0r3 Solaris 2.7 & 2.8
6.0r1 Solaris 2.7 & 2.8
6.0 Solaris 2.7 & 2.8
5.2.2r1 Solaris 2.7 & 2.8
5.2.2 Solaris 2.7 & 2.8
5.2.1 Solaris 2.7 & 2.8
5.2r7 Solaris 2.7 & 2.8
5.2r2 Solaris 2.7 & 2.8
5.2r1 Solaris 2.7 & 2.8
4.2.1r8 Solaris 2.6 & 2.7
Hope this helps
Michael Hester