Issues caused by the mysqldump version

mysqldump5.1 version

Mysqldump--version

Mysqldump Ver 10.13 Distrib 5.1.73, for Redhat-linux-gnu (x86_64)

Mysqldump--help | grep Gtid

No content

mysql5.6 version

Mysqldump--version

Mysqldump Ver 10.13 Distrib 5.6.25, for Linux (x86_64)

Mysqldump--help | grep Gtid

--set-gtid-purged[=name]

When exporting Mysql5.6 with mysqldump5.1, add--set-gtid-purged=off

will appear

Mysqldump:unknown variable ' set-gtid-purged=off '

Change to 5.6

# mysqldump-u-p-h Test > Bak.sql

Mysqldump:got Error:1356:view References Invalid table (s) or column (s) or function (s) or definer/invoker of View lack R Ights to use them when doing LOCK TABLES

When a backup is created, the table object referenced by the View object does not exist, and execution of the lock tables fails, so mysqldump aborts

Attach the--force parameter when executing mysqldump, which is ignored when an error is encountered and continues with the subsequent operation

Issues caused by the mysqldump version