Re: Mysqldump unusable, bugged?
matt_lists wrote: matt_lists wrote: Found the problem now we have this added on a few tables in the dump DATA DIRECTORY='E:\mysql\data\campbell\' INDEX DIRECTORY='E:\mysql\data\campbell\' the restore barfs on this not sure how to remove this, looking at options now, it only puts this on a couple tables, not all of them Definitly the problem, but I cant find the option to remove it If I replace it with the following it works fine DATA DIRECTORY='E:\\mysql\\data\\campbell\\' INDEX DIRECTORY='E:\\mysql\\data\\campbell\\' works great in test, wont work in production, the backup sql file is 20-60 gig depending on the site, there's no way I can search and replace that size a file Anybody know? Is there some option I'm not setting which causes the data directory and index directory to not be correct? Why are there not hundreds of people with this problem, I would think it affects anyone on 4.x running on a windows machine, I hope they dont learn the hard way when a restore fails to work! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump unusable, bugged?
On Tue, 1 Feb 2005, matt_lists wrote: now we have this added on a few tables in the dump DATA DIRECTORY='E:\mysql\data\campbell\' INDEX DIRECTORY='E:\mysql\data\campbell\' DATA DIRECTORY='E:\\mysql\\data\\campbell\\' INDEX DIRECTORY='E:\\mysql\\data\\campbell\\' Anybody know? Is there some option I'm not setting which causes the data directory and index directory to not be correct? Why are there not hundreds of people with this problem, I would think it affects anyone on 4.x running on a windows machine, I hope they dont learn the hard way when a restore fails to work! Noone has found a way to reproduce it with 100% certainity. If you have a way to always reproduce, feel free to re-open my bug at: http://bugs.mysql.com/bug.php?id=6660 (Or send me the test-case and I can do it). I haven't gotten the bug approved since I can't reproduce it (but it does happen quite often, just haven't been able to find out why, not even by replaying binary logs). cheers, Tobias -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump unusable, bugged?
Tobias Asplund wrote: On Tue, 1 Feb 2005, matt_lists wrote: now we have this added on a few tables in the dump DATA DIRECTORY='E:\mysql\data\campbell\' INDEX DIRECTORY='E:\mysql\data\campbell\' DATA DIRECTORY='E:\\mysql\\data\\campbell\\' INDEX DIRECTORY='E:\\mysql\\data\\campbell\\' Anybody know? Is there some option I'm not setting which causes the data directory and index directory to not be correct? Why are there not hundreds of people with this problem, I would think it affects anyone on 4.x running on a windows machine, I hope they dont learn the hard way when a restore fails to work! Noone has found a way to reproduce it with 100% certainity. If you have a way to always reproduce, feel free to re-open my bug at: http://bugs.mysql.com/bug.php?id=6660 (Or send me the test-case and I can do it). I haven't gotten the bug approved since I can't reproduce it (but it does happen quite often, just haven't been able to find out why, not even by replaying binary logs). cheers, Tobias I can repeat it every time, but only when I dump all tables, if I specify the bad tables that cause the problem, the extra parameters are not included I cant post my entire database due to security concerns if I dump only the affected table, the bug does not appear -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump unusable, bugged?
I've seen this quite a few times, but never been able to reproduce it properly. I'm assuming you're running on Windows, correct? I'd search your dump-file for DATA DIRECTORY the problem on Windows is that it uses \ instead of / in the path names there, which makes it use it as an escape character. Since dATA/INDEX DIRECTORY in CREATE TABLE is ignored on Windows when importing anyways, it's safe to remove those clauses. If you can find a way to reproduce it, feel free to add it to my old bug report about this at: http://bugs.mysql.com/bug.php?id=6660 cheers, Yes running windows I set all the sizes to match, 256mb and I still get the same error, tried dumping 2 different databases from 2 different machines, identical structures but different data, same error I checked line 2153 and found no '\m' or anything else out of the ordinary -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump unusable, bugged?
matt_lists wrote: I've seen this quite a few times, but never been able to reproduce it properly. I'm assuming you're running on Windows, correct? I'd search your dump-file for DATA DIRECTORY the problem on Windows is that it uses \ instead of / in the path names there, which makes it use it as an escape character. Since dATA/INDEX DIRECTORY in CREATE TABLE is ignored on Windows when importing anyways, it's safe to remove those clauses. If you can find a way to reproduce it, feel free to add it to my old bug report about this at: http://bugs.mysql.com/bug.php?id=6660 cheers, Yes running windows I set all the sizes to match, 256mb and I still get the same error, tried dumping 2 different databases from 2 different machines, identical structures but different data, same error I checked line 2153 and found no '\m' or anything else out of the ordinary You might find this useful: http://www.vim.org/tips/tip.php?tip_id=26 Vim uses the ^M notation, but I imagine that corresponds to \m. I have a program which can strip various newline characters out and replace with specified ones. If you'd like a copy, I could fish it out? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump unusable, bugged?
Found the problem now we have this added on a few tables in the dump DATA DIRECTORY='E:\mysql\data\campbell\' INDEX DIRECTORY='E:\mysql\data\campbell\' the restore barfs on this not sure how to remove this, looking at options now, it only puts this on a couple tables, not all of them -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump unusable, bugged?
matt_lists wrote: Found the problem now we have this added on a few tables in the dump DATA DIRECTORY='E:\mysql\data\campbell\' INDEX DIRECTORY='E:\mysql\data\campbell\' the restore barfs on this not sure how to remove this, looking at options now, it only puts this on a couple tables, not all of them Definitly the problem, but I cant find the option to remove it If I replace it with the following it works fine DATA DIRECTORY='E:\\mysql\\data\\campbell\\' INDEX DIRECTORY='E:\\mysql\\data\\campbell\\' works great in test, wont work in production, the backup sql file is 20-60 gig depending on the site, there's no way I can search and replace that size a file -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump unusable, bugged?
On Thu, 27 Jan 2005, matt_lists wrote: Having repeatable problems doing restores, 4.1.8 and 4.1.9 both do the same error Is there some setting I'm missing? mysqldump -u username-pPassword --all-databases --quote-names /intranet/backup/backup.sql E:\intranet\backupmysql -u xotech -pDaredevil22 -f backup.sql ERROR at line 2153: Unknown command '\m'. ERROR at line 2153: Unknown command '\m'. ERROR at line 2153: Unknown command '\m'. mysql: Out of memory (Needed 626767192 bytes) mysql: Out of memory (Needed 626763096 bytes) E:\intranet\backup I've seen this quite a few times, but never been able to reproduce it properly. I'm assuming you're running on Windows, correct? I'd search your dump-file for DATA DIRECTORY the problem on Windows is that it uses \ instead of / in the path names there, which makes it use it as an escape character. Since dATA/INDEX DIRECTORY in CREATE TABLE is ignored on Windows when importing anyways, it's safe to remove those clauses. If you can find a way to reproduce it, feel free to add it to my old bug report about this at: http://bugs.mysql.com/bug.php?id=6660 cheers, -- Tobias Asplund [EMAIL PROTECTED] Trainer and Consultant, Sweden MySQL AB http://www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysqldump unusable, bugged?
Having repeatable problems doing restores, 4.1.8 and 4.1.9 both do the same error Is there some setting I'm missing? mysqldump -u username-pPassword --all-databases --quote-names /intranet/backup/backup.sql E:\intranet\backupmysql -u xotech -pDaredevil22 -f backup.sql ERROR at line 2153: Unknown command '\m'. ERROR at line 2153: Unknown command '\m'. ERROR at line 2153: Unknown command '\m'. mysql: Out of memory (Needed 626767192 bytes) mysql: Out of memory (Needed 626763096 bytes) E:\intranet\backup -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysqldump unusable, bugged?
This could be a case where your dump files are not split in such a way so that they honor the max_packet_length setting of the recieving server. Make sure you tell mysql dump what the maximum size of an INSERT statement will be for the server you want to read the dump into or it will put all of the data for the entire table into a single INSERT statement. Shawn Green Database Administrator Unimin Corporation - Spruce Pine matt_lists [EMAIL PROTECTED] wrote on 01/27/2005 01:13:21 PM: Having repeatable problems doing restores, 4.1.8 and 4.1.9 both do the same error Is there some setting I'm missing? mysqldump -u username-pPassword --all-databases --quote-names /intranet/backup/backup.sql E:\intranet\backupmysql -u xotech -pDaredevil22 -f backup.sql ERROR at line 2153: Unknown command '\m'. ERROR at line 2153: Unknown command '\m'. ERROR at line 2153: Unknown command '\m'. mysql: Out of memory (Needed 626767192 bytes) mysql: Out of memory (Needed 626763096 bytes) E:\intranet\backup -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
