mysqldump acting strange

[Robert Biddle]

For some reason your mysqldump program is causing dumps to be exported with the following in them:

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!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' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

Additionally, trying to import any dump of any kind will produce these same errors. No dumps of any format seem to successfully import.

Here are the types of commands that I have used:

mysqldump -u root -h localhost dbname < dbfile.sql

This failed to import a dump produced by PHPMyAdmin.

I created a very simple sql statement and put it in a .sql file and tried to import that instead. The simple file only included the text "CREATE TABLE BR_images (xid int(10) NOT NULL default '0');"

This caused the same errors as listed above.

I tried some compatibility settings to help lessen possible error problems. When I use the option --compatible=mysql40, then I reduce the number of errors. It does not reduce the error count however if I change compatibility to mysql322.

I've never seen anything like this before. The system cannot even import its own dumps that it exports.

This is running on MySQL 5.0.19 on a Windows 2003 machine.



Edited 1 time(s). Last edit at 05/13/2006 09:41PM by Robert Biddle.