Bug #24556 | mysqldump --all-databases does not dump all databases | ||
---|---|---|---|
Submitted: | 23 Nov 2006 20:05 | Modified: | 5 Dec 2006 22:51 |
Reporter: | Martijn Wenke | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0.27 | OS: | Windows (Win 2003 server) |
Assigned to: | CPU Architecture: | Any | |
Tags: | --all-databases, mysqldump, windows 2003 |
[23 Nov 2006 20:05]
Martijn Wenke
[24 Nov 2006 11:10]
Valeriy Kravchuk
Thank you for a problem report. Please, send SHOW PROCESSLIST results next time when you are dumping all the databases. Are you sure no other users are working with databases when you are making a dump?
[24 Nov 2006 13:09]
Valeriy Kravchuk
Is it a fresh install of 5.0.27 or you had different version before? Had you installed MySQL server as a member of local Administrators group on Windows? (Error 13 is "Permission denied", hence the question.)
[26 Nov 2006 19:19]
Martijn Wenke
>Is it a fresh install of 5.0.27 or you had different version before? I don't know exacty I installed the MySQL softare at the first time. I had an older version running. Some time ago I removed the new version and installed it again. I exported the tables with SQLYog and imported them in the fresh installed MySQL. Sometimes I think the server is a little bit slow: for example a takes some time after closing an application a file is "unlocked" so I can delete it. Is there a way to get verbose/debug info in a log file? > Had >you installed MySQL server as a member of local Administrators group on >Windows? Yes, I used an admin account
[30 Nov 2006 15:03]
Martijn Wenke
It look' s McAfee VirusScan Enterprise 8 causes the problems. Maybe it locks (during scanning) some temporary files while mysqldump tries to edit/open or delete them. I turned of this setting of the "On Access scanner": "When reading from disk" So the real time scanner, scans files during tests only by this way: "When writing to disk" During the tests all backups/dumps are 100% OK Used McAfee scan engine: 5100 Patch level: 14
[3 Dec 2006 9:21]
Valeriy Kravchuk
Closed as not a result of a bug in MySQL's code.
[5 Dec 2006 22:51]
Martijn Wenke
Last time the scheduled backup script was running the backup was not OK again! Part of the log file (generated by the script): "** Logging MySQL processes... *************************** 1. row *************************** Id: 3 User: root Host: localhost:1381 db: NULL Command: Query Time: 0 State: NULL Info: SHOW FULL PROCESSLIST ** Creating backup using mysqldump ... Dump finished - checking D:\Backup\MySQL_DB\all-databases.sql ... OK, dump file is found! ** Analyzing dump file D:\Backup\MySQL_DB\all-databases.sql ... --- Checking dump file for databases: USE `decision`; USE `joomla`; --- Checking dump file for completion time: ** Show all databases in MySQL system ... *************************** 1. row *************************** Database: information_schema *************************** 2. row *************************** Database: decision *************************** 3. row *************************** Database: joomla *************************** 4. row *************************** Database: margarita-trade *************************** 5. row *************************** Database: mysql *************************** 6. row *************************** Database: reservering *************************** 7. row *************************** Database: test" You can see mysqldump does skip some databases: margarita-trade, mysql, reservering & test. So can anyone tell me how to log verbose/debug information to the logfile? Regards, Martijn