IM002][unixODBC][Driver Manager]Data source name not found, and no default driver specified [ISQL]ERROR: Could not SQLConnect

If  trying isql from server gives the following error,

IM002][unixODBC][Driver Manager]Data source name not found, and no default driver specified
[ISQL]ERROR: Could not SQLConnect


Then check the results of following commands in servers

odbcinst -q -s

odbcinst -q -d

if you find any error means that the server is unable to read both odbc.ini and odbcinst.ini files. To resolve this configure the environment variable of server as 

export ODBCSYSINI=/etc/

export ODBCINI=/etc/odbc.ini

this should fix the error.

Comments

Post a Comment

Popular posts from this blog

CDbConnection failed to open the DB connection mysql 8

Image
While accessing web configured with mysql 8 and php and you see the following error: CDbConnection failed to open the DB connection: SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client OR  PHP Fatal error:  Uncaught PDOException: PDO::__construct(): The server requested authentication method unknown to the client [caching_sha2_password]  It maybe due to  PHP devs might have not implemented the MySQL's 8.0 connection protocol ( auth with caching_sha2_password ) within the newer PHP versions. If you want to use mysql >= 8 and you dont care about caching_sha2_password,  If you are running a fresh install of mysql 8, just select the second option as shown in the image. Otherwise, you need to  configure MySQL 8.0 to run in mysql_native_password mode. As it can't configured in my.cnf, change the user profile as:- ALTER USER 'mysqlUsername'@'localhost' IDENTIFIED WITH mysql_native_password BY 'mysqlUse
Read more

/bin/sh^M: bad interpreter: No such file or directory Linux

While running a script in Linux, if you encounter an error such as : /bin/sh^M: bad interpreter: No such file or directory The error is due to incorrect format of the script. Most probably when the script is created in Windows and transferred to Linux. The script might have a dos line ending file. The clue is the ^M Inorder to resolve this error: Open the script in Linux using vim editor,  enter in vi command mode (key ESC), then type this: : set fileformat = unix   Finally save it :x! or :wq! Thats it! Try running the script again and the error would have disappeared.  
Read more