Simon Kerr Posted August 29 Posted August 29 I'm getting the following error when trying to upgrade to the latest build. Any suggestions as to what I need to tweak to overcome this? Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs /home/saw7z54jegas/public_html/applications//setup/upg_/queries.json - query #5
DawPi Posted August 29 Posted August 29 The issue might be due to using MyISAM tables, which have a lower row size limit. To address this problem, you should first convert the tables to InnoDB and then try again. Marc 1
Simon Kerr Posted August 30 Author Posted August 30 (edited) Thanks, gave that a try as my db was MyISAM and have now updated to InnoDB. Still getting the same error though 😞 Is there an easy way to tell what table the error is referring to? Edited August 30 by Simon Kerr
Marc Posted August 30 Posted August 30 Check if you are using compact table types too (you shouldnt be)
Simon Kerr Posted September 7 Author Posted September 7 (edited) Compression is set to off on the server Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs /home/saw7z54jegas/public_html/applications//setup/upg_/queries.json - query #5 Edited September 7 by Simon Kerr
Jim M Posted September 7 Posted September 7 Apologies, we are referring to the row format, not compression. InnoDB has 2 commons row formats, compact and dynamic. You will want to ensure you're using dynamic.
teraßyte Posted September 7 Posted September 7 9 minutes ago, Jim M said: You will want to ensure you're using compact. I think you mean dynamic row format. 😋
Jim M Posted September 7 Posted September 7 6 minutes ago, teraßyte said: I think you mean dynamic row format. 😋 Not enough coffee this morning, thank you 🙂 teraßyte 1
Simon Kerr Posted September 12 Author Posted September 12 (edited) They all appear to be set to dynamic Engine Version Row_format Rows Avg_row_length Data_length Max_data_length Index_length Data_free Auto_increment Create_time Update_time Check_time Collation Checksum Create_options Comment Max_index_length Temporary ibf_advert_ads InnoDB 10 Dynamic 1 16384 16384 0 0 0 3 2024-08-29 23:41:29 NULL NULL utf8mb4_unicode_ci NULL 0 N Edited September 12 by Simon Kerr
Marc Posted September 12 Posted September 12 What version is it you are upgrading from? And coudl you let me know if you have now reverted to your backup?
Simon Kerr Posted September 13 Author Posted September 13 All sorted now and it was the Engine that was causing me the issue. For some reason not all of the tables updated and once rectified it upgraded like a dream! Thank you so much for your help and assistance.
Recommended Posts