Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
NilR
Post Patron
Post Patron

OdbcErrors SQL0445W Value "2602 " has been truncated

Any one knows why I get below error with PBI Desktop when I run my query but not in Toad?

 

DataSource.Error: ODBC: SUCCESS_WITH_INFO [01004] [IBM][CLI Driver][DB2/AIX64] SQL0445W Value "2602 " has been truncated. SQLSTATE=01004

Details:
DataSourceKind=Odbc
OdbcErrors=[Table]

2 ACCEPTED SOLUTIONS
v-eqin-msft
Community Support
Community Support

Hi @NilR ,

 

It may caused by the large table/data . Please try to optimize the data model to reduce the data size, like remove unnecessary columns, remove deplicate rows...

 

For more information, please refer to:

Optimization guide for Power BI - Power BI | Microsoft Docs

Eyelyn9_0-1637198608545.png

 

Best Regards,
Eyelyn Qin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

I realized some of my columns have null and it throw exception unless I clean up the data and convert them all to something like string. so, I did COALESCE([field],"NULL")  and this fixed the error. not sure if it is a good solution but it fixed mine.

View solution in original post

2 REPLIES 2
v-eqin-msft
Community Support
Community Support

Hi @NilR ,

 

It may caused by the large table/data . Please try to optimize the data model to reduce the data size, like remove unnecessary columns, remove deplicate rows...

 

For more information, please refer to:

Optimization guide for Power BI - Power BI | Microsoft Docs

Eyelyn9_0-1637198608545.png

 

Best Regards,
Eyelyn Qin
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

I realized some of my columns have null and it throw exception unless I clean up the data and convert them all to something like string. so, I did COALESCE([field],"NULL")  and this fixed the error. not sure if it is a good solution but it fixed mine.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.