Bug #32631 mysqldump unable to dump multiple innodb tables in a single statement
Submitted: 22 Nov 2007 16:58 Modified: 22 Dec 2007 17:48
Reporter: Vikas Bhatti Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server: mysqldump Command-line Client Severity:S3 (Non-critical)
Version:10.9 Distrib 4.1.11 OS:Linux (Debian Sarge 3.1)
Assigned to: CPU Architecture:Any
Tags: innodb, mysqldump

[22 Nov 2007 16:58] Vikas Bhatti
I am currently trying to make a copy of all the innodb tables I currently have in a database. However, I keep getting either 'segmentation fault' or 'Error 1146: table xx.xx doesn't exist when doing LOCK TABLES'. 

How to repeat:
The command I'm trying is:

mysqldump --single-transaction -u 'username' --port 3307 'dbname' --tables ''table1', 'table2', 'table...' > innodb_dump.sql

Where all of the tables are using innodb.

Suggested fix:
The workaround is to issue a dump, one table at a time. This seems to run fine and can be easily scripted. Dumping multiple MyISAM tables in a single statement runs perfectly fine too.
[22 Nov 2007 17:19] Heikki Tuuri
This is a command-line client bug.
[22 Nov 2007 17:48] Valeriy Kravchuk
Please, try to repeat with a newer version of mysqldump, from version 4.1.22 at least, and inform about the results.
[23 Dec 2007 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".