Mysql – Issue on thesqldump in MySQL5.6

MySQLmysql-5.6mysqldump

I did upgrade the MySQL server from 5.5 to 5.6

I am trying to take dump for a table like this

 mysqldump -uroot -p dba admin > D:\admin.sql

But it gets following error

mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1':
You have an er ror in your SQL syntax; check the manual that
corresponds to your MySQL server v ersion for the right syntax to use
near 'OPTION SQL_QUOTE_SHOW_CREATE=1' at line 1 (1064)

edit:

mysqldump verison is 5.5.30.

Best Answer

Some information can be found in SET Syntax and this bug.

The SET statement assigns values to different types of variables that affect the operation of the server or your client. Older versions of MySQL employed SET OPTION, but this syntax is deprecated in favor of SET without OPTION.

How to fix it

If the problem happens when you are creating the dump (your case): Upgrade you MySQL client tools to the same version of your MySQL server (in your case, 5.6)
If the problem happens when you are restoring the dump: At the beginning of the file, you have some SET OPTION statements; edit your dump, and change all instances of SET OPTION to SET SESSION like described here

Related Solutions

Mysql – phpMyAdmin Error After Upgrade to 3.5.8.1

I had this problem as well, when downgrading phpMyAdmin. When I deleted my cookies, the problem went away.

Mysql – Problems migrate database from 4 to 5.5 thesql

This should be as simple as piping the output of mysqldump through a utility that can manipulate the data stream with a regular expression pattern match, like sed or perl.

mysqldump [options] | perl -pe 's/^\)\sTYPE=InnoDB/) ENGINE=InnoDB/' > dumpfile.sql

For any line that begins with ) TYPE=InnoDB this will replace the starting portion of the line with the new string ) ENGINE=InnoDB and leave the rest of the line intact. It won't do anything to lines that don't match (they'll pass right through).

For quick and simple validation that this does what you want, use the --no-data option in mysqldump to dump only the table structures, not the data, and examine the resulting file. If it looks right, you can repeat the process without --no-data.

A similar expression in sed should be this:

mysqldump [options] | sed 's/^) TYPE=InnoDB/) ENGINE=InnoDB/' > dumpfile.sql

...however, I'm not as conversant in sed as I am in perl, so I'd recommend the first approach, although I tested both versions and they appear to work identically.

Both perl and sed should be already present on any *nix system, and both are freely downloadable for Windows. On Windows, you'll probably need " rather than ' surrounding the expressions.