ERROR 1118 (42000): Row size too large (> 8126)

timblack1

I exported a MySQL database from Webfaction, and tried to import it into MariaDB on OpalStack, using the following command: /home/timblack1/tools/wfmigrate/maria/import.sh. That produces the following error:

ERROR 1118 (42000): Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.

This error and its solution are described at https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb/.

When I try that page's methods to determine which table has the problem via /home/timblack1/tools/wfmigrate/maria/rowsize.sh, I get the following error:

ERROR 1227 (42000) at line 1: Access denied; you need (at least one of) the PROCESS privilege(s) for this operation

This prevents me from discovering which table needs to be fixed.

I tried running rowsize.sh with the same database in a local MySQL instance, it outputs the following:

`No tables with rows size too large found.
0 tables found with row size too large.

./rowsize.sh done.`

What can I do to successfully import this database?

Tim

sean

timblack1

A customer here had a similar problem around a year ago. We compared our MariaDB config and variable dump with the same info from his own server and we weren't able to determine why his DB wouldn't import here.

The solution he went with was to edit his SQL to change the large VARCHAR fields in his DB to TEXT, as the error message suggested.

If that's not an option for you, then maybe a private MariaDB instance would help? You'd be able to tweak all of the DB server config which might help you find a solution.

kierenp

Not sure how helpful this is but...

Are you doing like for like import/exports? For example, are you using MyISAM or InnoDB in both places and not drifting between storage engines by not being explicit and the two setups have different defaults?

Also, are you specifying character sets on export rather than relying on the client default? For example, if you export as utf8mb4 but try and import as utf8 then I think you might hit this error due to the former being 4 bytes per char and the latter being 3 bytes.

Can you dump the schema (i.e. without data) of the WF db, import the schema into Opalstack and then redump and do a diff on the files? That will confirm any structural differences.

I wonder if innodb_page_size differs between WF and Opalstack?

I recently moved a database from WF to Opalstack but did so by just running the mysqldump on WF and then the mysql import etc on Opalstack on the command line directly. I'm not sure what the migrate script does but might be worth trying this with the specific commands instead.

timblack1

sean kierenp Thank you for your help. Replacing varchar(255) with TEXT for certain lines in the file created by mysqldump which were specified by the mysql import command's error messages fixed the problem for me.

sean

timblack1 awesome, glad that worked for you 🙂