User Profile
Sai_Akash
New Member
Joined 1 year ago
User Widgets
Contributions
DataSource.Error: MySQL: Out of memory; check if mysqld or some other process uses all available mem
Hi BI Team, I’m encountering an "Out of Memory" error when trying to connect Power BI to my MySQL database hosted on AWS RDS. The error message suggests checking if mysqld or another process is using all available memory, and mentions using 'ulimit' or adding more swap space. Has anyone faced this issue before? If so, what steps did you take to resolve it? Any advice on adjusting memory settings in either Power BI or MySQL would be greatly appreciated. Regards, Sai AkashSolved555Views0likes3CommentsDataSource.Error: MySQL: Out of memory; check if mysqld or some other process uses all available
Hi BI Team, I’m encountering an "Out of Memory" error when trying to connect Power BI to my MySQL database hosted on AWS RDS. The error message suggests checking if mysqld or another process is using all available memory, and mentions using 'ulimit' or adding more swap space. Has anyone faced this issue before? If so, what steps did you take to resolve it? Any advice on adjusting memory settings in either Power BI or MySQL would be greatly appreciated. Regards, Sai AkashSolved1KViews0likes1CommentRe: OLE DB or ODBC error: [DataFormat.Error] We couldn't convert to Number
Hi Hashadapu, Thanks for the information above, it's valuable. I’m encountering an issue with one of the columns, as shown in the attached screenshot. Could you please take a look and help me figure out what's going wrong? Thanks for the support and information in advance! Regards, Sai Akash3.9KViews0likes1CommentRe: Error returned: 'OLE DB or ODBC error: [DataFormat.Error] We couldn't convert to Number....
Hi Miguel Félix, I hope you're doing well. I followed the advice to check for any incorrect format in the columns, specifically looking for cases where text might be present where numbers are expected. I applied the suggested approach by creating a new column with the syntax: try Number.FromText([id]) otherwise "ABC" However, despite this, I'm still facing the same issue even with the id column. I’m unable to isolate the rows causing the errors, and the problem persists. If possible, could I get some additional personal support to resolve this issue? I’d really appreciate it if we could discuss this further in a direct message. Thanks so much for your help! Best regards, Sai Akash482Views0likes0CommentsRe: OLE DB or ODBC error: [DataFormat.Error] We couldn't convert to Number...
Hi Pete, Thank you for your suggestion! I followed your advice and checked the query, focusing on columns that are being converted to a number type during the transformation. However, even when I specifically applied this to the id column, I’m still encountering the same issue. I went to the Home tab, selected the “Keep Errors” option, and despite this, I’m unable to isolate the root cause of the conversion error for this column. Would you be able to provide further guidance or suggest additional steps I can take to troubleshoot this? If possible, I’d like to discuss this in a DM personally to explore potential solutions more efficiently. Thanks again, Sai Akash1.5KViews0likes1CommentRe: Error returned: 'OLE DB or ODBC error: [DataFormat.Error] We couldn't convert to Number....
Hi Miguel Félix, Thank you for your suggestion. I have attempted to implement the approach by creating a new column using the syntax try Number.FromText([Column1]) otherwise "ABC". Unfortunately, despite this adjustment, I am still unable to resolve the issue. It seems the problem persists, and I am unable to isolate the specific rows causing the errors, likely due to data format discrepancies that are not immediately apparent in the Power Query sample. Given the challenges I’m facing, I would greatly appreciate any additional personal assistance or guidance to help resolve this issue effectively. Thank you. Sai Akash483Views0likes0CommentsError returned: 'OLE DB or ODBC error: [DataFormat.Error] We couldn't convert to Number....
I'm facing an issue when importing multiple files into Power Query in Power BI. I've tried different file formats (CSV, Excel, TXT) and removed unnecessary columns, but the problem persists. Even though I’ve set the correct data types for each column, some files either fail to load. This inconsistency is happening across different files, and I’m unable to automate the process properly. Any suggestions or solutions to ensure consistent file imports with the correct transformations would be greatly appreciated.522Views0likes3CommentsOLE DB or ODBC error: [DataFormat.Error] We couldn't convert to Number...
I'm facing an issue when importing multiple files into Power Query in Power BI. I've tried different file formats (CSV, Excel, TXT) and removed unnecessary columns, but the problem persists. Even though I’ve set the correct data types for each column, some files either fail to load. This inconsistency is happening across different files, and I’m unable to automate the process properly. Any suggestions or solutions to ensure consistent file imports with the correct transformations would be greatly appreciated.Solved1.6KViews0likes7CommentsOLE DB or ODBC error: [DataFormat.Error] We couldn't convert to Number
I'm facing an issue when importing multiple files into Power Query in Power BI. I've tried different file formats (CSV, Excel, TXT) and removed unnecessary columns, but the problem persists. Even though I’ve set the correct data types for each column, some files either fail to load. I’m unable to automate the process properly. Any suggestions or solutions to ensure consistent file imports with the correct transformations would be greatly appreciated.Solved4KViews0likes6Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.