Download Mysql Odbc 5.1 Driver

0 views

Skip to first unread message

Alexandrie Gallup

unread,

Aug 5, 2024, 10:49:11 AM8/5/24

to seoviemisdist

Anerror message from Data Direct ODBC drivers for MySQL is shown when trying to connect to MySQL Community Servers database using DataStage ODBC enterprise stage or trying to import the table definition from the same database.IBM Information...

I had tried installing the mysql-connector-odbc_8.0.22-1ubuntu18.04_amd64.deb package and it had complained about not finding the mysql-community-client-plugins package. I tried a few variations of apt-cache search mysql-community-client-plugins to locate this additional package but nothing came up.

I have gone through the following steps to install from the more generic unix files - MySQL :: MySQL Connector/ODBC Developer Guide :: 4.2.2 Installing Connector/ODBC from a Binary Tarball Distribution

The Amazon Web Services (AWS) ODBC Driver for MYSQL is now generally available for use with Amazon RDS and Amazon Aurora MySQL-compatible edition database clusters. This database driver provides support for faster switchover and failover times, and authentication with AWS Secrets Manager or AWS Identity and Access Management (IAM).

\nThe Amazon Web Services (AWS) ODBC Driver for MYSQL is a standalone driver and supports RDS and community MySQL 8.X and Amazon Aurora MySQL version 3.X. You can install the aws-mysql-odbc package for Windows, Mac or Linux by following established installation guides in GitHub. The driver relies on monitoring the database cluster status and being aware of the cluster topology to determine the new writer. This approach reduces switchover and failover times from tens of seconds to single digit seconds compared to the open-source driver.

\nThe AWS Advanced MySQL ODBC driver is released as an open-source project under version 2 of the GNU General Public License (GPL v2). For more details click here to view Getting Started instructions and guidance on how to raise issues.

The Amazon Web Services (AWS) ODBC Driver for MYSQL is a standalone driver and supports RDS and community MySQL 8.X and Amazon Aurora MySQL version 3.X. You can install the aws-mysql-odbc package for Windows, Mac or Linux by following established installation guides in GitHub. The driver relies on monitoring the database cluster status and being aware of the cluster topology to determine the new writer. This approach reduces switchover and failover times from tens of seconds to single digit seconds compared to the open-source driver.

The AWS Advanced MySQL ODBC driver is released as an open-source project under version 2 of the GNU General Public License (GPL v2). For more details click here to view Getting Started instructions and guidance on how to raise issues.

When I look at the ODBC Data Source Administrator on my desktop (where the query fails), the drivers tab shows 2 MySQL drivers: MySQL ODBC 5.3 ANSI Driver and MySQL ODBC 5.3 Unicode Driver. I tried uninstalling the MySQL drivers and installing the latest MySQL drivers with the same error.

Sounds like a bug in Toad Data Point. We bundle our own mySQL drivers, so the error you are getting should not be a problem. What version are you using? Can you download the latest Toad Data Point, which is 4.1?

Yes, I am attempting to run the query in TDP. Yes, windows is a 64 bit version. I did uninstall the MySQL ODBC drivers, and installed the 64 bit MySQL ODBC drivers. The download file is entitled: mysql-connector-odbc-5.3.7-winx64. Do you think I need to reinstall using a different file?

I am presently working on a MySQL database. Trying to connect remotely to the server from my client computer using LabVIEW 18. I have tried many configurations along the way, however my UDL won't connect itself to the MySQL server and it's subsequent databases. I have made sure to install or update anything that may cause an architecture mismatch(ODBC drivers, Visual Studio, etc.), which I had hoped would be the answer, but woefully it is not. Any help to get this moving in an appropriate direction would be greatly appreciated.

Go to Settings -> ODBC (64-bit) on the client computer and add a System DSN reference. You can specify all the details of the connection and even test it. Save this to dsn file and refer to it n LabVIEW.

I have done this exact thing previously but as RolfK suggested being aware of the variance between 32 and 64 bit odbc sources. I followed your instructions to the letter except using the 32 bit odbc, because I am running 32 bit LV as well as 32 bit Data Connectivity Toolkit. I was able to create the system DSN with a successful connection, although I had to create a new user name on my server side, because for whatever reason the access was denied to my previous login, even though all the same permissions are granted. Still however, the issues persist. When creating the UDL to put into the path for the data connect open in my VI. I select my newly created system DSN from the data source list, enter my credentials and receive the error.... "Test Connection failed because of an error in initializing provider. Catastrophic failure"

MySQL is now maintained (owned?) by Oracle, and Microsoft never supported MySQL and now will even less likely. Rather the hell is freezing over first. In the past I always simply setup a connection in the ODBC Admin (right bitness) and then collected the settings from the registry entry and directly passed a connection string with those settings to the ODBC interface. I'm using my own ODBC driver usually, but that should also just work for the Database Toolkit.

It appeared the most logical provider to select on the data link properties as my data source is an ODBC and ALL of the options available on my provider list are Microsoft....Is there a way to create a new provider? Or some other option for me to choose? Am I just missing something(completely possible, haha)?

I am already using the MySQL ODBC Driver 5.1 and use it to create my System DSN with a successful connection during data source creation. It is in the process of creating the UDL that I get the error messages and cannot connect.

If you need other options to configure your server connection, try them out in ODBC Admin and store them to a DSN. Then check in the registry under "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBC.INI\" what settings are all there and add them to the above string.

If you have a configured DSN Name you can also just pass that name to the DB Tools Open Connec (String).vi but if you work with a fixed driver and database setup I usually prefer to hardcode those settings in the LabVIEW code and avoid having people to edit ODBC DSN entries.

AFAIK, Everything you can configure in ODBC can be specified in the connection string. At least a proper connection string can connect to SQLServer, Access or Excel just fine without ODBC. I don't know about MySQL, it might depend on the library you're using.

I'm currently trying to get access to some MYSQL and PostgreSQL databases via an ODBC connection via an ODBC Administrator GUI as I had on Windows. After searching around, I have only found scattered and old tutorials for installing and setting up ODBC connections on Ubuntu.

You should always periodically copy your production environment to a test environment for user training and a development environment for yourself. You don't want your trials and errors effecting production (the company's bottom line) or user training (they are already enough challenge day to day without messing up their world).

Get and install the MySQL drivers from MySQL here: That will create the files libmyodbc5X (where the X depends on which driver has been installed) and libodbcmy.so in /usr/lib/x86_64-linux-gnu/odbc. The first one is the driver, the second is the managing driver (not very useful).

Create two files in /etc: odbcinst.ini and odbc.iniThe first one contains the specification of the available drivers. In your case, there will be two of them, one for MySQL, the other one for Postgres. The second one is the collection of database source name. Each one specifies at least a name, between brackets [], and a driver name.

From that point on, you can connect just using the DSN name (Prod or TestDB). Of course, it might be wise to put your username/password elsewhere. The exact way to connect to DSN depends on the programming language/development tool that you use.

There are no headers on the functions as they should be pretty easy to understand anyway. The functions that I have written are named after the PHP counterparts since I use them a lot and they make sense to me.

Good timing for me because I need to start working on a MySQL app to talk to a remote database, but my utility will be run from many different locations and bringing along an install of ODBC is really not going to be practical.

I think I see the problem. In the included udf file, it doesn't just define functions, it also calls __mysql_odbc() looking for a MySQL installed driver and if none is found, it sits spinning in an endless loop. In my case here, I see that this machine doesn't currently have a MySQL ODBC driver installed.

*GERMAN* [note: you are not allowed to remove author / modified info from my UDFs]My UDFs:[_SetImageBinaryToCtrl] [_TaskDialog] [AutoItObject] [Animated GIF (GDI+)] [ClipPut for Image] [FreeImage] [GDI32 UDFs] [GDIPlus Progressbar] [Hotkey-Selector] [Multiline Inputbox] [MySQL without ODBC] [RichEdit UDFs] [SpeechAPI Example] [WinHTTP]UDFs included in AutoIt: FTP_Ex (as FTPEx), _WinAPI_SetLayeredWindowAttributes