MySQL Row Size Too Large

[azadhussnain]

Hello, myclients are facing an sql error Row Size Too Large while importing an sql file in phpmyadmin or via backup wizard.

here is my /etc/my.cnf :

[mysqld]
performance-schema = 0
datadir = /var/lib/mysql
socket = /var/lib/mysql/mysql.sock
symbolic-links = 0
log-error = /var/log/mysqld.log
pid-file = /var/run/mysqld/mysqld.pid
innodb_buffer_pool_size = 134217728
max_allowed_packet = 268435456
open_files_limit=80000
innodb_file_per_table = 1
innodb_log_file_size = 512M

please tell me how can i increase mysql roz file limit ? i am running mariadb 10.3 with mysql governor and cloudlinux.

i read all forums and all threads but didn't found an accurate or an final solution.
please tell me any final and accurate solution

 

[andrew.n]

What is the exact error you are getting when you import the database?

 

[cPRex]

As @andrew.n was hinting at, there are a few different "row size" errors, but I'm guessing you are running in to one of the two mentioned here:

Troubleshooting Row Size Too Large Errors with InnoDB

Fixing "Row size too large (> 8126). Changing some columns to TEXT or BLOB may help."

mariadb.com

Can you check that page to see if that helps you resolve the issue?

 

[azadhussnain]

As @andrew.n was hinting at, there are a few different "row size" errors, but I'm guessing you are running in to one of the two mentioned here:

Troubleshooting Row Size Too Large Errors with InnoDB

Fixing "Row size too large (> 8126). Changing some columns to TEXT or BLOB may help."

mariadb.com

Can you check that page to see if that helps you resolve the issue?

sir my client is getting the error, and this is a production server. a lot of data is stored. i have checked the article you sent but it's out of my understanding, what i have to do from my end?
client is saying in another hosting company it is working fine.
can you tell me the solution which i can do from my end

 

[cPAdminsMichael]

@cPRex is already linking to a page describing the issue and how to fix it
Issue is probably that your client is moving from a database NOT running in strict mode, and yours ARE running in strict mode (default in later versions of MySQL/MaraDB)

 

[cPRex]

@azadhussnain - there is not an easier fix available for the issues you are seeing. If that fix doesn't work, or if you are not able to apply it, you may want to speak with your hosting provider to see if they can check the server and get you more details.