Forum Discussion
MySQL Fatal Data Read Error During Power BI Refresh (OLE DB or ODBC Error)
Hi all,
I'm facing a persistent issue while refreshing my Power BI dashboard that's connected to MySQL.
Problem:
When I run a full refresh, I get errors in the following tables:
DAX Tables
DimAFMapping
Prod-Cat-Subcat
Customer
However, when I refresh these tables individually, the DAX tables refresh successfully without any errors.
The issue persists in the following tables:
Cust_new
FactReciept
FactRecieptitem
Prod_Cat_Subcat
Error message:
OLE DB or ODBC error: [DataSource.Error] MySQL: Fatal error encountered during data read.
Additional info:
Using MySQL Connector/ODBC for the connection.
- This issue only occurs during certain refreshes — sometimes the tables load, sometimes they fail.
- .NET & ODBC Connectors are already installed
Has anyone faced this kind of issue before? Could this be due to:
Network instability?
Timeout settings?
Server-side MySQL configurations?
These are the errors, when I run a full refresh
It occurs when I run each tables individually.
NB: These refresh was working till last week.
Any advice or troubleshooting suggestions would be really helpful.
Thanks in advance!
Hi v-priyankata and v-ssriganesh ,
Issue is resolved now. I just tried re-configuring the MySQL Installer Community.
Thank you
9 Replies
- v-priyankataCommunity Support
Thank you for reaching out to the Microsoft Fabric Forum Community.
amitchandak Thanks for the inputs.
Check the MySQL logs to see if there are any clues about why connections are failing. try bumping up the timeout settings so Power BI doesn’t lose connection during long data loads.
Make sure you're using the latest version of the MySQL ODBC driver it can fix bugs and improve stability. Schema changes - Double-check if any tables or columns were changed or removed in MySQL that could break your Power BI queries.
Thnaks.- v-priyankataCommunity Support
I hope the information provided was helpful. If you still have questions, please don't hesitate to reach out to the community.
- v-priyankataCommunity Support
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
- amitchandakSuper User
Suryamaxillian , is there any change in the schema, or did you change the case sensitivity(Table level) on MySQL, that can have this issue