Concurrent Threads Calling Connector/ODBC SQLGetData Cause Memory Corruption/Crash
(Doc ID 2557276.1)
Last updated on SEPTEMBER 27, 2019
Applies to:MySQL Connectors - Version 5.3 and later
Information in this document applies to any platform.
One client thread calling SQLGetData() works fine, but memory corruption and/or crash occurs when > 1 thread are running.
Since the symptoms are easier to see on 32-bit, check if application or Connector/ODBC had recently been converted from 64-bit.
Similarly, check if the connection string had NO_LOCALE changed from 1 to 0. And see if application recently converted from single thread to multithread.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document