Fwd: Re: Driver could not be loaded (0) SQLSTATE=IM002 - Mailing list pgsql-odbc
From | Srimathi Chandrasekaran |
---|---|
Subject | Fwd: Re: Driver could not be loaded (0) SQLSTATE=IM002 |
Date | |
Msg-id | 1145970978.444e2122ee838@rmc60-231.urz.tu-dresden.de Whole thread Raw |
List | pgsql-odbc |
----- Forwarded message from Srimathi Chandrasekaran <Srimathi.Chandrasekaran@mailbox.tu-dresden.de> ----- Date: Tue, 25 Apr 2006 15:15:22 +0200 From: Srimathi Chandrasekaran <Srimathi.Chandrasekaran@mailbox.tu-dresden.de> Reply-To: Srimathi Chandrasekaran <Srimathi.Chandrasekaran@mailbox.tu-dresden.de> Subject: Re: [ODBC] Driver could not be loaded (0) SQLSTATE=IM002 To: Ludek Finstrle <luf@pzkagis.cz> hello I have set the environmental variables for each session. I have set the ODBCINIDIR as $GLOBUS_LOCATION/var I have specified the odbcini for the session in which i have iodbctest echo $ODBCINI /usr/local/globus-4.0.1/var/odbc.ini $GLOBUS_IODBC_PATH/bin/iodbctest iODBC Demonstration program This program shows an interactive SQL processor Driver Manager: 03.52.0406.0126 Enter ODBC connect string (? shows list): rli1000 1: SQLDriverConnect = [iODBC][Driver Manager]Data source name not found and no default driver specified. Driver could not be loaded (0) SQLSTATE=IM002 1: ODBC_Connect = [iODBC][Driver Manager]Data source name not found and no default driver specified. Driver could not be loaded (0) SQLSTATE=IM002 I have gone through the paragraph whatever u have sent. Whether i have to create another odbc.ini in /etc directory (copy of odbc.ini that is located in /usr/local/globus-4.0.1/var/odbc.ini )? may be i will try the new version also. regards srimathi.c Quoting Ludek Finstrle <luf@pzkagis.cz>: > > psqlodbc-07.03.0200 > > quite old. You could try 07.03.026X version from pgfoundry.org. > > > I want to know whether my installation was correct. > > 1.I have set the environmental varaibles as follows > > setenv GLOBUS_LOCATION0/usr/local/globus-4.0.1 > > # setenv GLOBUS_IODBC_PATH $GLOBUS_LOCATION > > # setenv ODBCINI $GLOBUS_LOCATION/var/odbc.ini > > The # char mean comment out the line? > Do you specify it in each session? Or do you specify only for install? > > > 2. for libiodbc-3.52.4 > > I have done everything as a root > > > > % ./configure --prefix=$GLOBUS_IODBC_PATH --disable-gtktest > --with-pthreads > > --disable-gui --with-iodbc-inidir=$ODBCINIDIR (i have set ODBCINDIR > variable > > I see no $ODBCINIDIR definition. I see only definition of $ODBCINI. > > > But when i run the iodbctest > > Do you have specified in this session $ODBCINI? > > > $GLOBUS_IODBC_PATH/bin/iodbctest "DSN=lrc1000;UID=dbuser;PWD=" > > iODBC Demonstration program > > This program shows an interactive SQL processor > > Driver Manager: 03.52.0406.0126 > > 1: SQLDriverConnect = [iODBC][Driver Manager]Data source name not found and > no > > default driver specified. Driver could not be loaded (0) SQLSTATE=IM002 > > FAQ for iODBC says: > > [iODBC][Driver Manager]Data source name not found and no default driver > specified. Driver could not be loaded, SQLSTATE=IM002 > > There are several reasons why this message could occur. The best solution > is to trace through what's happening: your application has been linked > against libiodbc, which has tried to find an odbc.ini file one way or > another - either through the ODBCINI environment variable or the fall-back > paths (typically /etc/odbc.ini, depending on how it was compiled). You > should check that such a file exists in a suitable location, and that > it is accessible (particularly if your application runs with different > user privileges - such as apache/php running as a www-data user). > > Additionally, it could be that iODBC has found a suitable odbc.ini file, > but none of the file(s) found contain the DSN you've requested. Check > the syntax of your request - is the ODBC connect-string correct, and > does the DSN you're requesting exist? See also the section of this > FAQ, above, entitled `What's an odbc.ini and what do I put in it?'. > > Regards, > > Luf > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > ----- End forwarded message -----
pgsql-odbc by date: