Bug #32563 mysqldump no data dumped
Submitted: 21 Nov 2007 9:04 Modified: 9 Sep 2008 7:02
Reporter: Azeddine ESSAI Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S1 (Critical)
Version:5.1, 5.0, 6.0 BK OS:Linux (REDHAT ES4)
Assigned to: CPU Architecture:Any
Tags: mysqldump, regression

[21 Nov 2007 9:04] Azeddine ESSAI 
Description:
Hello,

I'm migrating my application from aix server to a linux server.
I try to dump the table "commande" with this command :
mysqldump -h aixserver -u xxx -pxxx  -y  -v --compatible=mysql323 Base commande
but I have this message :

-- Connecting to aixserver...
-- MySQL dump 10.13
--
-- Host: aixserver    Database: Base
-- ------------------------------------------------------
-- Server version 3.23.58-log
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO,MYSQL323' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
-- Retrieving table structure for table commande...
-- Skipping dump data for table 'commande', it has no fields
-- Disconnecting from aixserver...
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;

-- Dump completed on 2007-11-21  8:39:32

regards

How to repeat:
mysql cluster 5.1 on REDHAT ES4
dumping from an AIX5L server
[21 Nov 2007 10:36] Sveta Smirnova 
Thank you for the report.

Please provide output of SHOW CREATE TABLE commande and accurate version of MySQL you use
[21 Nov 2007 12:59] Azeddine ESSAI 
mysql> SHOW CREATE TABLE commande;
+----------+--------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              ----+
| Table    | Create Table                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+----------+--------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              ----+
| commande | CREATE TABLE `commande` (
  `nom` varchar(8) NOT NULL default '',
  `environnement` varchar(32) NOT NULL default '',
  `type_env` char(1) NOT NULL default '',
  `details` varchar(64) default NULL,
  `consignes` varchar(64) default NULL,
  PRIMARY KEY  (`nom`)
) TYPE=MyISAM COMMENT='Table des commandes batchs' |
+----------+--------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              --------------------------------------------------------------------------------                                              ----+
1 row in set (0.00 sec)
[21 Nov 2007 13:09] Azeddine ESSAI 
I dump data from Mysql 3.23.58 basis(the old server).
The dump work good with the new server(Linux) on : 
- Mysql Cluster 5.0.37(community)
- Mysql Cluster 5.2.3
- Mysql Cluster 6.0.2
but not with Mysql Cluster 5.1.22(community).
It's strange.
[21 Nov 2007 13:38] Sveta Smirnova 
Thank you for the feedback.

>I dump data from Mysql 3.23.58 basis(the old server).

Does it mean you dump from MySQL 3.23.58 server using mysqldump from MySQL 5.1 package?
[21 Nov 2007 13:45] Azeddine ESSAI 
yes.
I do this :
[root@linuxserver] mysqldump -h aixserver -u xxx -pxxx  -y  -v --compatible=mysql323 Base

on the aixserver : Mysql 3.23.58
on the Linuxserver : Mysql Cluster 5.1.22
[22 Nov 2007 7:54] Sveta Smirnova 
Thank you for the report.

Verified as described.

Version 5.0.45 works fine, althought both 5.0 and 5.1 BK sources contain this problem.
[7 May 2008 15:10] Thomas Seifert 
Is there any work being done on this bug?
It really stumped me to see (nearly) empty backups from the mysql4.0 servers which were done through mysql5 clients after upgrading.
do we have to stay with older versions of mysql5.0 to keep this working?
[9 May 2008 16:43] Brian Porter 
Also stung by this bug. Any updated information available?
[16 May 2008 11:10] Jure Špik 
This bug should be assigned to someone since it is critical, verified and almost a year old.
[20 May 2008 15:01] Brian Porter 
Boy do I agree. This is a critical component of our installation! (And I'm sure that is true for many others as well.)

Bug is also confirmed using mysqldump from [Ver 10.11 Distrib 5.0.51a, for portbld-freebsd6.3 (i386)] against a MySQL database server [Ver 12.22 Distrib 4.0.20, for unknown-openbsd3.6 (i386)] installation.
[20 Jun 2008 12:51] Hubert Nowinski 
Same problem on version 5.0.54 @ Gentoo Linux.

(Mysql  Ver 14.12 Distrib 5.0.54, for pc-linux-gnu (i686) using readline 5.2)
(Portage 2.1.4.4 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.6.1-r0)
[20 Jun 2008 12:59] Hubert Nowinski 
...and exactly the same on 5.0.56 @ Gentoo Linux.

(mysql  Ver 14.12 Distrib 5.0.56, for pc-linux-gnu (i686) using readline 5.2)
(mysqldump  Ver 10.11 Distrib 5.0.56, for pc-linux-gnu (i686))
[20 Aug 2008 14:48] Francesco Ciocchetti 
Hitting the same bug here.

Mysqldump 5.0.51a from a mysql4.0.27 Server. 

Is anyone working on this bug? Is almost 1 year old and S1 but does not look to be assigned to anyone.

Thanks
Francesco
[9 Sep 2008 7:02] Domas Mituzas 
Duplicate of Bug#34192 which is closed already.