techblog.jj-it.de - Access to MySQL Database: Connector/ODBC Installation

Access to MySQL Database: Connector/ODBC Installation

Techblog.jj-it.de Spined HTML

Wangleto MySQL Database: Connector/ODBC Installation Skip to contentJoachim Jäckel MenuHomeContactWangleto MySQL Database: Connector/ODBC Installation Contents1 Connector/ODBC Installation1.1 Prerequisites1.2 Install from rpm1.3 Missing Dependencies2 Configure unixODBC2.1 Configure dsn in odbc.ini2.2 Test the configured dsn3 Troubleshooting3.1 Some typical errormessages4 Next StepTo wangle a MySQL Database via unixODBC you need a driver. You get it self-ruling from http://dev.mysql.com/.Connector/ODBC InstallationPrerequisitesunixODBC should be installed first, see Unix ODBC InstallationInstall from rpmFor popular Linux distributions rpm packages are misogynist at http://dev.mysql.com/downloads/connector/odbc/ For RedHat Linux and for Oracle Linux there are Packages in the standard repositiories. These are usually oder versions.The pursuit examples use Version 5.3.4 from dev.mysql.com.Missing DependenciesIf there is no unixODBC Package from your Linux distibution vendor installed, the installation may goof with dependency errors:dependency problems # rpm -i mysql-connector-odbc-5.3.4-1.sles11.x86_64.rpm error: Failed dependencies: libodbc.so.2()(64bit) is needed by mysql-connector-odbc-5.3.4-1.sles11.x86_64 libodbcinst.so.2()(64bit) is needed by mysql-connector-odbc-5.3.4-1.sles11.x86_641234# rpm -i mysql-connector-odbc-5.3.4-1.sles11.x86_64.rpm            error: Failed dependencies:        libodbc.so.2()(64bit) is needed by mysql-connector-odbc-5.3.4-1.sles11.x86_64        libodbcinst.so.2()(64bit) is needed by mysql-connector-odbc-5.3.4-1.sles11.x86_64If this happens, you can use spare options for rpm:rpm -i --nodeps --noscripts # rpm -i --nodeps --noscripts mysql-connector-odbc-5.3.4-1.sles11.x86_64.rpm1# rpm -i --nodeps --noscripts mysql-connector-odbc-5.3.4-1.sles11.x86_64.rpmConfigure unixODBCNext step is to integrate the MySQL Connector/ODBC into unixODBC.Configure dsn in odbc.iniThe file odbc.ini in usually located /usr/local/etc/odbc.ini, /etc/odbc.ini, /etc/unixODBC/odbc.ini. If you have compiled unixODBC from source as described in the previous article, you will use /usr/local/etc/odbc.ini.For each connection a datasource name dsn is configured in odbc.inisample datasource in odbc.ini ; mysqltestdsn is the datasource name (not specimen sensitive) [mysqltestdsn] ; driver: unixODBC will use the specified suburbanite suburbanite = /usr/lib64/libmyodbc5w.so ; server: hostname (or ip address) of your MySQL Server server = mysqlserver ; port: database port number on the specified host (usually 3306) port = 3306 ; database: name of database database = sakila ; charset: weft set of MySQL database, usually latin1 or utf8 charset = utf8123456789101112; mysqltestdsn is the datasource name (not specimen sensitive)[mysqltestdsn]; driver: unixODBC will use the specified driverdriver          = /usr/lib64/libmyodbc5w.so; server: hostname (or ip address) of your MySQL Serverserver          = mysqlserver; port: database port number on the specified host (usually 3306)port            = 3306; database: name of databasedatabase        = sakila; charset: weft set of MySQL database, usually latin1 or utf8charset         = utf8Test the configured dsnThe configured dsn can be tested with isql: /usr/local/bin/isql (if your compiled unixODBC from source) or /usr/bin/isql (unixODBC installed as package)sample isql connection $ reverberate "select version();" | /usr/local/bin/isql -v mysqltestdsn username password +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------------------------+ SQL> +----------------+ | version() | +----------------+ | 10.0.21-MariaDB| +----------------+ SQLRowCount returns 1 1 rows fetched SQL> 1234567891011121314151617$ reverberate "select version();" | /usr/local/bin/isql -v mysqltestdsn username password+---------------------------------------+| Connected!                            ||                                       || sql-statement                         || help [tablename]                      || quit                                  ||                                       |+---------------------------------------+SQL> +----------------+| version()      |+----------------+| 10.0.21-MariaDB|+----------------+SQLRowCount returns 11 rows fetchedSQL>sample isql connection: query weft set $ /usr/local/bin/isql mysqltestdsn username password +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------------------------+ SQL> SELECT schema_name, default_character_set_name FROM information_schema.SCHEMATA; +-----------------------------------------------------------------+---------------------------------+ | schema_name | default_character_set_name | +-----------------------------------------------------------------+---------------------------------+ | information_schema | utf8 | | other_db | latin1 | | sakila | utf8 | +-----------------------------------------------------------------+---------------------------------+ SQLRowCount returns 2 3 rows fetched12345678910111213141516171819$ /usr/local/bin/isql mysqltestdsn username password+---------------------------------------+| Connected!                            ||                                       || sql-statement                         || help [tablename]                      || quit                                  ||                                       |+---------------------------------------+SQL> SELECT schema_name, default_character_set_name FROM information_schema.SCHEMATA;+-----------------------------------------------------------------+---------------------------------+| schema_name                                                     | default_character_set_name      |+-----------------------------------------------------------------+---------------------------------+| information_schema                                              | utf8                            || other_db                                                        | latin1                          || sakila                                                          | utf8                            |+-----------------------------------------------------------------+---------------------------------+SQLRowCount returns 23 rows fetchedHere you see three schema_names which can be accessed by the MySQL User. But: with ODBC the user only can wangle the default database (sakila in the example).TroubleshootingSome typical errormessagesisql errormessageReason[ISQL]ERROR: Could not SQLConnectuse isql -v to get a increasingly detailed message[IM002][unixODBC][Driver Manager]Data source name not found, and no default suburbanite specifiedWrong datasource name or file odbc.ini not found[S1000][unixODBC][MySQL][ODBC 5.3(w) Driver]Access denied for user 'username'@'%' to database 'sakila'Wrong database name in odbc.ini or user has no access-rights[S1000][unixODBC][MySQL][ODBC 5.3(w) Driver]Access denied for user 'username'@'oraserver.local' (using password: YES)Wrong username or wrong passwordNext StepIf the isql Test works, your are ready to configure the Oracle Gateway to ODBC and the Database Link in your Oracle Database: Configure Oracle Gateway for ODBC with MySQL ConnectorLeave a Reply Cancel replyYour email write will not be published. Required fields are marked *CommentName * Email * Website Search for: SearchPagesOracle Gateway to ODBCUnix ODBC InstallationAccess to MS SQL Server Database: FreeTDS InstallationConfigure Oracle Gateway for ODBC with FreeTDSAccess to MySQL Database: Connector/ODBC InstallationConfigure Oracle Gateway for ODBC with MySQL ConnectorAccess to Informix Database: Informix ODBCSuburbaniteInstallationConfigure Oracle Gateway for ODBC with Informix ODBC DriverRecent Posts Gateway from Oracle to Informix Gateway from Oracle to MySQL Gateway from Oracle to MS SQL ServerAbout me Consultant for Databases, Linux/Unix, High Availabiltiy. German Homepage www.jj-it.de ContactHomeContact Joachim Jäckel Proudly powered by WordPress