Bug #36858 5.1.24mysqldump issues nasty error when dumping database from mysql 4.0.x server

• Submitted: 21 May 2008 19:20
• Modified: 10 Nov 2008 20:23
• Reporter: Arkadiusz Miskiewicz (Basic Quality Contributor)
• Status: Won't fix
• Category: MySQL Server: mysqldump Command-line Client
• Severity: S3 (Non-critical)
• Version: 5.1.24, 5.1, 6.0 BK
• OS: Any
• CPU Architecture: Any
• Tags: qc

[21 May 2008 19:20] Arkadiusz Miskiewicz

Description:
Dumping database from 4.0 server using mysqldump from 5.1.24 causes:

The only options were: mysqldump --quick --quote-names ...

mysqldump: Error: 'Something is wrong in your syntax obok 'SELECT DISTINCT LOGFILE_GROUP_NAME FROM INFORMATION_SCHEMA.FILES' w linii 1' when trying to dump tablespaces

How to repeat:
Do what described above.

Suggested fix:
Don't try to dup information_schema on 4.0 servers.

[21 May 2008 20:18] Sveta Smirnova

Thank you for the report.

But  mysqldump --quick --quote-names ... exits with
Usage: mysqldump [OPTIONS] database [tables]
OR     mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...]
OR     mysqldump [OPTIONS] --all-databases [OPTIONS]
For more options, use mysqldump --help

Please provide full command you use to invoke mysqldump

[21 May 2008 20:29] Arkadiusz Miskiewicz

/usr/bin/mysqldump --defaults-file=/root/.my.cnf-abc -h $server --quick --quote-names mydatabase > out

where .my.cnf-abc contains host + user + password only

[22 May 2008 20:27] Sveta Smirnova

Thank you for the feedback.

Verified as described:

../mysql-5.1.24-rc-linux-i686-glibc23/bin/mysqldump --socket=/tmp/mysql_ssmirnova.sock -uroot test >/dev/null
mysqldump: Error: 'You have an error in your SQL syntax.  Check the manual that corresponds to your MySQL server version for the right syntax to use near 'SELECT DISTINCT LOGFILE_GROUP_NAME FROM INFORMATION_SCHEMA.FILE' when trying to dump tablespaces

[2 Aug 2008 18:15] Hartmut Holzgraefe

Had this with 6.0.6 mysqldump and a 4.1 server ... the actual dump seems to be ok though so we might consider lowering this to D4?

[10 Nov 2008 20:23] Omer Barnir

Given the simple workaround of using the 4.0 mysqldump client to do the dump (and not the 5.1 one), this issue will not me fixed

[5 Apr 2011 0:39] Rick James

The spurious message about "SELECT DISTINCT LOGFILE_GROUP_NAME FROM INFORMATION_SCHEMA.FILE" persists in mysqldump 5.1.36 (dumping 4.0.26 database)

[14 Dec 2011 8:47] carlos leal

Add --no-tablespaces to solve the problem