Getting erratically Error 7357 - Connector 8.0.28 (2 replies)

March 26, 2023, 11:12 pm

≫ Next: Duplicated rows when select from a tabla with PK. STRANGE (1 reply)

≪ Previous: unable to load mysql ODBC 8.0 unicode driver on Excel for mac (3 replies)

$

0

0

I'm connecting from SQL Server 2019, through MySQL Connector ODBC 8.0.28
to a MySQL 8.0.17 DB

At night, a job that consist of several steps, is fired. Each step retrieves new rows from a specific table. Steps could retrieve no rows, one row, or 4 million rows

Eventually and erratically, some step fails, giving error 7357 Can't access object, and then following steps finish with error 730 Can't execute the query

Sometimes only happens the first error

At morning, when I get notified about the error, I re-run the job, and it finishes ok

It mostly happens when getting tables of million-scale rows (about 2,3,4,5M rows). However today is happening with small queries too (less than 10K rows)


The MySQL DB is a replica. I don't have much information about the replication method. But I can say that in this replica/slave, tables have AUTO_INCREMENT columns (maybe with this information you can realize what sync method is being used)

---

Duplicated rows when select from a tabla with PK. STRANGE (1 reply)

March 26, 2023, 11:09 pm

≫ Next: possible memory leak connector version 8.0.32 and up (4 replies)

≪ Previous: Getting erratically Error 7357 - Connector 8.0.28 (2 replies)

$

0

0

I'm sennding a simple :

select * from myDb.myTable

the table has a PK, unique key

It returns *duplicated* entries for the same key. That's impossible


I then checked the Connector Setup, I realized the PREFETCH was enabled

When I turned it off, queries started to work



What the PREFETCH option does?


NOTE:

The server is an online replica, and the table gets several insert by second

My task is to read that replica (instead of the prod server) and send data to a data warehouse

possible memory leak connector version 8.0.32 and up (4 replies)

August 31, 2023, 9:18 am

≫ Next: Problems with Umlaute/UTF8 with MySQL Connector 8.0 (1 reply)

≪ Previous: Duplicated rows when select from a tabla with PK. STRANGE (1 reply)

$

0

0

Hello,

We just noticed what looks like a memory leak in the driver starting with version 8.0.32.
After commit:
"
WL#15178 - INTERNAL: Refactoring of internal ODBC structures (Part 1, lists and arrays)

Change-Id: Ie39caf9c64ec5ad9fac3caf65f0f65a2051f8fd1
"

the destructor for STMT no longer calls delete_param_bind which was supposed to free the param bind buffers.

Could you please let me know if there is something I am missing?

If there is in fact a memory leak, could you please tell me if there is any work-around and what would be the fastest way to get help with this.

Thank you,
Bogdan Vasilescu
bogdan_mabo@live.com

Problems with Umlaute/UTF8 with MySQL Connector 8.0 (1 reply)

June 20, 2023, 5:09 pm

≫ Next: Inserting a record is very slow and fails with database with 20k+ records (1 reply)

≪ Previous: possible memory leak connector version 8.0.32 and up (4 replies)

$

0

0

Hi there, I'm pulling data from my Wordpress database (charset utf8mb4_unicode_ci) via MySQL Connector 8.0 into MS Access. This has worked well until I had to restore a backup on my website using Duplicator Backup Plugin. Now, all German Umlaute (ä, ü etc.) and other letters like ß are displayed incorrectly in Access (e.g. Ãœbersetzung instead of Übersetzung). I already installed the newest Connector version, I added CHARSET=utf8mb4 to my connection string (see below), nothing helped. Is there somthing else I can do? Thanks for help. Frank

Constr = "Driver=MySQL ODBC 8.0 Ansi Driver;" & _
"Server=" & server & "; User = " & user & ";Password = " & pw & ";Database=" & datenbank & "; CHARSET=utf8mb4"

Inserting a record is very slow and fails with database with 20k+ records (1 reply)

June 12, 2023, 7:57 pm

≫ Next: You have an error in your SQL syntax; check the manual that corresponds (3 replies)

≪ Previous: Problems with Umlaute/UTF8 with MySQL Connector 8.0 (1 reply)

$

0

0

Hi. I've been using MySQL Server 5.7 for a number of years without any issues. Client PCs use MySQL ODBC connector 5.1. I use a legacy MFC application that adds records to the database. As I mentioned, this has worked for a number of years. I started seeing that when the total number of records reaches 20k+, the application was unable to add new records. The application's debug log shows an ODBC error but it isnt obvious as to the cause. For example, on one system running Windows 10 it shows:

COM EXCEPTION Error
Code = 80040e21
Code meaning = IDispatch error #3105
Source = Microsoft OLE DB Provider for ODBC Drivers
Description = ODBC driver does not support the requested properties.

I have a second client PC that is running the same application with the same ODBC Connector version but on Windows 7 and it is able to add the records.

I have to admit that I am not very familiar with MySQL and its configuration. My guess is that there must be some timeout or buffer setting that I have not set. I just dont know which. I noticed that it takes between 10 and 15 seconds for the insert command to fail.

I played around with some of the timeout settings but they did not make any difference.

Eventually, I started deleting records from the database. Once I had deleted 2k records, suddenly, the application on the Windows 10 system was able to add a record. This makes me believe that there must be a timeout or buffer setting I'm missing.

The client application I'm using is an MFC application that uses OLEDB to connect connect and add/modify/fetch records. Before adding, it checks to see if a record already exists for a specific key. If not, then it adds it. Ocasionally it will fetch a record.

When MySQL Server was installed, it was configured as follows:
-Detailed Configuration
-Server Machine
-Transactional Database Only
-Decision Support (DSS)/OLAP
-Enable TCP/IP Networking (port 3306)
-Enable Strict Mode
-Standard Character Set
-Installed as a Windows Service

This has worked for me for several years. It wasnt until one client PC was upgraded from Windows 7 to Windows 10 that we ran into this problem. Also, even on the Windows 7 system it takes several seconds to add a record (>10sec). This doesnt seem right and I fear that if the database continues to grow, eventually the Windows 7 system will also fail the same way.

I hope that I've included enough information. If anyone has any clue what may be happening, please let me know.

Thanks in advance.

Regards,
LA

You have an error in your SQL syntax; check the manual that corresponds (3 replies)

July 20, 2023, 1:48 am

≫ Next: Microsoft Access with ODBC-Connector 8 (5 replies)

≪ Previous: Inserting a record is very slow and fails with database with 20k+ records (1 reply)

$

0

0

I am having great trouble creating a data pipeline using MySQL connector 8 with SSIS. I can view the tables, but it gives me this error: "TITLE: Microsoft Visual Studio ------------------------------

ERROR [42000] You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '"sample_table"' at line 1 Error at Data Flow Task [ADO NET Source [16]]: System.Data.Odbc.OdbcException (0x80131937): ERROR [42000] [ma-3.1.18][10.4.24-MariaDB]You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '"sample_table"' at line 1 at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader, Object[] methodArguments, SQL_API odbcApiMethod) at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader) at System.Data.Odbc.OdbcCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.ReinitializeMetaData() at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostReinitializeMetaData(IDTSManagedComponentWrapper100 wrapper)

I am getting this error when Im using MySQL SQL specific, its the same issue with Mariadb although i use SQL specific to the db.

Microsoft Access with ODBC-Connector 8 (5 replies)

November 15, 2023, 4:50 am

≫ Next: Every new machine blocks connection (11 replies)

≪ Previous: You have an error in your SQL syntax; check the manual that corresponds (3 replies)

$

0

0

For about 15 years we have been using MySQL to store data for MS Access frontends. Until about 3 years ago in version 5.3, since then in version 8.0 with the latest release.

As driver we use the ODBC driver version 5.1.8 (32 bit), although this actually does not fit (anymore) to the MySQL server version.

A change to the current driver version (8.0.33) is not possible.

The driver "MySQL ODBC 8.0 Ansi Driver" often loses the connection to the data source during form filter functions in MS Access Forms. In my opinion, this driver is not suitable for use with MS Access as a frontend.

The driver "MySQL ODBC 8.0 Unicode Driver" on the other hand does not have the "quirks", but a serious bug. Whenever a primary key field contains a German special character (ä, Ä, ö, Ö, ü, Ü, ß), the data record is marked with an error and can no longer be selected or edited.

Maybe sometime in the distant future it will be possible to use the current ODBC driver for the current MySQL server version also under MS Access as frontend.

As we all know, hope dies last.

Many greetings
Stephan

Every new machine blocks connection (11 replies)

July 20, 2023, 1:54 am

≫ Next: UPgrade drivers and Keep settings (1 reply)

≪ Previous: Microsoft Access with ODBC-Connector 8 (5 replies)

$

0

0

Hello

It's hard do describe my problem, but we use Visual Basic 6 app, with 3.51.12 MySQL Connector/ODBC and 5.6.20 MySQL Server, all on Windows OS.

As you can see, this is a legacy system, and also this use root user for access.
Root has all the permissions, everything seems to be OK, just this weird issue.

Everytime a new machine opens our systems, and only for the first time of new machines, MySQL blocks all the new connections (from all machines, including server itself).

To solve, I have to go to the server, set the skip-grant-tables ON, reset the mysql service, connect to the database (without password), flush privileges, reset the password for root, flush privileges again, set skip-grant-tables OFF, reset the mysql service again, and now everything works great, including the new machine!

But after another new machine comes, the same goes again and again.

I have no idea what causes this. I was suspecting of being the password, but I can't change it. The password has 12 chars length and has the symbols of "!" and "#" on it. Dunno if this is the cause, but it's weird that everything is normal, but as soon as a new machine connects, it starts the problem.

Can someone help me find the problem?

Thanks.

---

UPgrade drivers and Keep settings (1 reply)

June 20, 2023, 5:02 pm

≫ Next: ODBC Driver compatibility with Windows Server 2008 64bit (1 reply)

≪ Previous: Every new machine blocks connection (11 replies)

$

0

0

I would like to keep the current settings under the ODBC (username and passowrd), would the MSI or Installer give me that? Does the MSI prompt for an upgrade or does it add another version of the drivers.
Currently running 8.0.30 looking to go to 8.0.33

thanks

ODBC Driver compatibility with Windows Server 2008 64bit (1 reply)

July 7, 2023, 4:49 am

≫ Next: Error while connecting MySQL (1 reply)

≪ Previous: UPgrade drivers and Keep settings (1 reply)

$

0

0

Hi,

We have a very old server Windows Server 2008 64 bit that uses ODBC for DB connection. There's a new project to setup a new MySQL 8.

I am tasked to validate the compatibility of the ODBC versions for MySQL that will work on this server. And if there are any pre-requisites to installing it?

Please advise.

Error while connecting MySQL (1 reply)

July 20, 2023, 2:00 am

≫ Next: Introducing the MySQL Configurator tool for Windows (no replies)

≪ Previous: ODBC Driver compatibility with Windows Server 2008 64bit (1 reply)

$

0

0

We are trying to connect MySQL database from excel.

We are trying Data -> Get Data -> From Database -> From MySQL Database.

While doing this we are getting error as below

Error
this connector requires one or more additional components to be installed before it can be used

Please help

Introducing the MySQL Configurator tool for Windows (no replies)

July 20, 2023, 9:07 am

≫ Next: ODBC 5.3 error (4 replies)

≪ Previous: Error while connecting MySQL (1 reply)

$

0

0

Introducing the MySQL Configurator tool for Windows
- https://blogs.oracle.com/mysql/post/introducing-the-mysql-configurator-tool

ODBC 5.3 error (4 replies)

August 7, 2023, 12:03 am

≫ Next: ODBC and remote server (3 replies)

≪ Previous: Introducing the MySQL Configurator tool for Windows (no replies)

$

0

0

I have choosed ODBC5.3 to connect remote mysql database version 5.7 from last year.It's worked perfectly until this monday.The error message is:[MySQL][ODBC 5.3(a) Driver]SSL connection error:protocol version mismatch.
This error occured in another office PC which belongs to the same LAN with mine.
I try to swtich to ODBC3.5 in IDE,it's useful.But I don't want to change source code.
There is ,in addition 5.3 worked well in my family.So I puzzled.
Someone could help me?

ODBC and remote server (3 replies)

August 7, 2023, 4:27 pm

≫ Next: ODBC for both server 5.x and 8.1 (no replies)

≪ Previous: ODBC 5.3 error (4 replies)

$

0

0

Using MySQL Workbench 8.0.25 64 bit I can connect my remote server 'Louhi' easily and manage my remote MySQL DB. Connection method is Standard TCP/IP over SSH (as I can see on page Manage Server Connections), localhost 127.0.0.1 and port 3306. But when I try to connect same server using ODBC, it don't work.

My workstation is 64 bit Windows 11.

I tried many ways, using SQLDriverConnect, SQLConnect, using SQLBrowseConnect to see connection attributes but without success.

How I can copy the Workbech connection attributes to ODBC to be able use my application written in C (using Visual Studio and ODBC functions) ?

ODBC for both server 5.x and 8.1 (no replies)

August 28, 2023, 7:19 am

≫ Next: Connecting MySQL DB to SSIS (no replies)

≪ Previous: ODBC and remote server (3 replies)

$

0

0

Hi, I'm thinking of migrating my mysql servers from version 5.x to 8.1, but it's impossible to migrate them all at once. That's why I would need windows computers to be able to work with any of those servers. I need an odbc capable of connecting to both 5.x and 8.1 servers. Is that possible?

---

Connecting MySQL DB to SSIS (no replies)

August 30, 2023, 12:44 pm

≫ Next: MySQL ODBC Connector Test Connection Failed (no replies)

≪ Previous: ODBC for both server 5.x and 8.1 (no replies)

$

0

0

I am currently trying to tie SSIS into a MySQL DB so I can retrieve data from it. I am trying to use the ADO.Net Source but in the Provider dropdown in the Connection Manager, when I select MySQL Data Provider, I get this error:

"Failed to find or load the registered .Net Framework Data Provider."

Haven't had any luck with resolving this and getting the MYSQL Data Provider to work.

MySQL ODBC Connector Test Connection Failed (no replies)

October 11, 2023, 1:58 am

≫ Next: CVE-2023-22102 - CVE-2023-3817 for MySQL Connector ODBC (1 reply)

≪ Previous: Connecting MySQL DB to SSIS (no replies)

$

0

0

Installed MySQL Connector/ODBC Driver (32-bit) on Windows Server 2022. Tried 8.0.33 and 5.3.13, both giving error when I do the Test Connection in the ODBC Data Source Setup screen.
It gives the error Connection Failed Malformed packet.

Did a ping and telnet both showing the server able to connect to the db server.
Please help.

CVE-2023-22102 - CVE-2023-3817 for MySQL Connector ODBC (1 reply)

November 9, 2023, 10:09 am

≫ Next: need help with odbc (4 replies)

≪ Previous: MySQL ODBC Connector Test Connection Failed (no replies)

$

0

0

Hello all,

We have a question regarding the SSI security vulnerability for Vulnerability:
CVE-2023-22102 - CVE-2023-3817

We are asking you if security fixes are already in progress for the MySQL Connector ODBC 8.2.0 for 32 bit product. (latest version for 32 bit is 8.0.35 currently).

We are facing an issue about security compliance auditor and we can't upgrade our application for 64 bits.

If it's already available, where can we download the 32 bit version for 8.2.0 MysQL Connector ODBC.


Best Regard.

need help with odbc (4 replies)

November 15, 2023, 9:40 am

≫ Next: ODBC- Excel- Working time (no replies)

≪ Previous: CVE-2023-22102 - CVE-2023-3817 for MySQL Connector ODBC (1 reply)

$

0

0

I downloaded mysql-connector-odbc-8.0.12-linux-glibc2.12-x86-64bit.tar.gz to install on debian 10. I created my odbc.ini and odbcinst.ini but when I try a datasource using iodbctest i get this
iodbctest myodbc
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0812.0326
1: SQLDriverConnect = [MySQL][ODBC 8.0(a) Driver]Failed to parse the incoming connect string. (0) SQLSTATE=HY000
1: ODBC_Connect = [MySQL][ODBC 8.0(a) Driver]Failed to parse the incoming connect string. (0) SQLSTATE=HY000

im lost lol. I installed it once in my lab many moons ago but dont remember how i got it to work. now im trying on another server without luck. Anyone has a pointer?

ODBC- Excel- Working time (no replies)

November 30, 2023, 2:35 am

≫ Next: ODBC Driver 8.0 slower than 5.3 (no replies)

≪ Previous: need help with odbc (4 replies)

$

0

0

AHi, I am solving the problem that when the working time exceeds 24 hours (we record it in hours), the ocdb connector reports a format error.

I need the working time to be in a format hh:mm:ss