ODBC success with info[01004]

[Augustin]

Hi,

When I try to import a table, I have this error message :

"DataSource.Error : ODBC: SUCCESS_WITH_INFO [01004] [MySQL][ODBC 5.3(w) Driver][mysqld-5.5.35-0+wheezy1]
Détails :
DataSourceKind=Odbc
DataSourcePath=dsn="name of my ODBC connector"
OdbcErrors=Table"

Don't understand because I can import the others table of my database without issue...

Do you know how can I fix that ?

Thank you

Sincerely,

Augustin

[Greg_Deckler]

01004 sounds like a data truncation error. Is this a very large table or is there a very large column definition?

[Augustin]

Thank you for your help !

This is a very large table (42 columns)... and there is a very large column definition too. Is this an issue ? 

[Augustin]

When I delete 4 columns type text (don't need this columns, commentary or things like that) it works...

So I can continue my work 🙂

It could be good for you to find the issue ... (because it works with QlikSense Desktop 😉 )

Good continuation !

Sincerely,

Augustin

[Greg_Deckler]

Glad you could get it worked out! 

[tristanstcyr]

We will fix this class of issue in an upcoming release.

We use batch row fetch with ODBC when it's available, which requires us to know in advance the size of a column in order to allocate a buffer in memory. We've seen that ODBC drivers very commonly return invalid column lengths, which leads us to allocate buffers that are too short to fit the entire column's value. This is why you're getting the error about truncation. We can't ignore the error, otherwise, you'd be getting the wrong data!

The fix will be to use row-by-row fetch by default and possibly add a flag for explicitly enabling batch-fetch when it's known to actually work well. We expect this to be in the May release.

In the meantime, the only work around is to not retrieve those columns.

Tristan St-Cyr

[yaznelita]

Hello!! i need this reports and i think i dont have a lot columns, Can I get back a version from the server?
while they solve the problem?

[yaznelita]

I was able to resolve by going back to the previous version of the server. May 2022

[jaimet561]

Hello tristanstcyr. 

Was the Issue fixed with the following releases? I use ODBC on a C Application that I created and I still get the Truncation Error.

The C application communicates with a Database to execute queries. If the query is a select statement, it returns the result of the query.

Can you give me some advice?

[tristanstcyr]

Hi jaimet561,

This error happens because the data was bound to a buffer that's smaller than the data being retrieved. You can either make the buffers larger or you can retrieve the data in chunks. You should be able to find information on how to do this online. Aside from that, the specifics of how to use ODBC in a C applicaiton are outside the topics on the Power BI forums. I'll concead though the ODBC C API can be dfficult to use...

Tristan

[jaimet561]

Hello tristanstcyr. Was the Truncation Error fixed with the release you mentioned? I used ODBC in a C appication and I still sometimes get a Truncation Error.

What can be done?

Thank you