[unixODBC-support] isql - No Connection, no error message, no log file

Wajid Baig wabmca at gmail.com
Wed Mar 13 18:56:25 GMT 2013


hi

Please do strace and redirect the STDOUT, STDERROR to a file. You may
try to see errors like some file not file or authorization issue by
yourself. If you cannot find the issue you can zip and post email the
output file.

Thanks,
Ahmed

On 3/13/13, Nico Grubert <nicogrubert at yahoo.de> wrote:
> Hi there
>
> I am trying to use the "isql" tool to test my ODBC data source.
> I have 2 different servers with different OS but with both identical
> odbc.ini files and unixODBC versions.
>
> Server A:
> Suse Linux Enterprise 10, 64 Bit
>
> Server B:
> Cent OS 6
>
> On both machines the command "isql --version" shows: unixODBC 2.2.11
>
> On "Server A" I can connect to the ODBC data source without any problem:
>
> Command:  isql -v my_odbc_data_source myuser mypass
> +---------------------------------------+
> | Connected!                            |
> |                                       |
> | sql-statement                         |
> | help [tablename]                      |
> | quit                                  |
> |                                       |
> +---------------------------------------+
> SQL>
>
> On "Server B" the same isql command does not work. I get the Linux
> prompt back without seeing any error message.
> Any idea what might be wrong?
>
> Trying to connect to a non-existing odbc data source results to:
> [S1090][unixODBC][Driver Manager]Invalid string or buffer length
> [ISQL]ERROR: Could not SQLConnect
>
> Regards & thanks a lot in advance
> Nico
> _______________________________________________
> unixODBC-support mailing list
> unixODBC-support at mailman.unixodbc.org
> http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
>


-- 

Sincerely
Baig
09176627037


More information about the unixODBC-support mailing list