database backup problem, since database over 60mb
Hello, I've got a problem with mysql 5 on my debian server. I've got a forum on this server and untill the database reached about 60 Mo I could dump the database with either phpmyadmin or with the command : mysql -u user -p'password' databasename backup_date.sql My last backup that worked was about 56Mb, but now since I've gone over the 60mb my backup files with phpmyadmin and mysqldump are only around 46Mb and therefore don't contain everything and also when I do a mysql -u user -p'password' databasename backup_date.sql it never finishes, and even if I wait for two hours the bacup_date.sql file is 0Mb ... The forum runs well and I use no compression I save the file in simple .sql text format. Any ideas as to why it does this or how I can fix it would be great ! I've gone through my my.cnf file and I can't see any setting that seems to block this. If you need any further information please let me know Thanks in advance, Richard -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: database backup problem, since database over 60mb
Richard, there's no inherent problem around 60 MB - I routinely dump data ranging from a few KB to a few GB. One thing I note is that you are using the mysql command, which is the interactive database client. You want to use mysqldump, the client program that dumps data from the database in SQL format. Why are you sure that a 46 MB dump doesn't contain everything? Granted, you have a dump in the last that was larger, but perhaps some unneeded data has been removed? Dan On 4/11/07, Richard [EMAIL PROTECTED] wrote: Hello, I've got a problem with mysql 5 on my debian server. I've got a forum on this server and untill the database reached about 60 Mo I could dump the database with either phpmyadmin or with the command : mysql -u user -p'password' databasename backup_date.sql My last backup that worked was about 56Mb, but now since I've gone over the 60mb my backup files with phpmyadmin and mysqldump are only around 46Mb and therefore don't contain everything and also when I do a mysql -u user -p'password' databasename backup_date.sql it never finishes, and even if I wait for two hours the bacup_date.sql file is 0Mb ... The forum runs well and I use no compression I save the file in simple .sql text format. Any ideas as to why it does this or how I can fix it would be great ! I've gone through my my.cnf file and I can't see any setting that seems to block this. If you need any further information please let me know Thanks in advance, Richard -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: database backup problem, since database over 60mb
Hi, Maybe you will have better luck with a command like: mysqldump -u user -ppassword databasename backup_date.sql Regarding phpmyadmin, my guess would be, the script is longer than the permitted time to finish. Defaults in php.ini is something like: max_execution_time = 30 ; Maximum execution time of each script, ; in seconds max_input_time = 60 ; Maximum amount of time each script may spend ; parsing request data memory_limit = 8M; Maximum amount of memory a script may ; consume (8MB) -- Later Mogens Melander +45 40 85 71 38 +66 870 133 224 On Wed, April 11, 2007 21:11, Richard wrote: Hello, I've got a problem with mysql 5 on my debian server. I've got a forum on this server and untill the database reached about 60 Mo I could dump the database with either phpmyadmin or with the command : mysql -u user -p'password' databasename backup_date.sql My last backup that worked was about 56Mb, but now since I've gone over the 60mb my backup files with phpmyadmin and mysqldump are only around 46Mb and therefore don't contain everything and also when I do a mysql -u user -p'password' databasename backup_date.sql it never finishes, and even if I wait for two hours the bacup_date.sql file is 0Mb ... The forum runs well and I use no compression I save the file in simple .sql text format. Any ideas as to why it does this or how I can fix it would be great ! I've gone through my my.cnf file and I can't see any setting that seems to block this. If you need any further information please let me know Thanks in advance, Richard -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Backup problem from 5.0 to mysql 4.1
I have local mysql 5.0 and I have developed an arabic site. The database encoding is utf8-bin. Localy everything work fine, all arabic text are displayed OK. Now I want to move it to a server in internet. The server has mysql 4.1 and as I restored the database there, some special arabic character are not displayed correctly. I don't know why only some character are inserted differently from others. Localy I have also tried to have both mysql server 4.1 5.0 to play with the backup and store, but without success, always the same result. Moving the binary database files (*.frm ...) from 5.0 to 4.1 doesn't work, it seem they are not compatible. I realy don't know what to do, it is hard to insert all data again, it is so big. Any help well be appreciated! -Amir -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Backup problem from 5.0 to mysql 4.1
From: Amir Bukhari Sent: 18 July 2006 09:23 I have local mysql 5.0 and I have developed an arabic site. The database encoding is utf8-bin. Localy everything work fine, all arabic text are displayed OK. Now I want to move it to a server in internet. The server has mysql 4.1 and as I restored the database there, some special arabic character are not displayed correctly. I don't know why only some character are inserted differently from others. Localy I have also tried to have both mysql server 4.1 5.0 to play with the backup and store, but without success, always the same result. Moving the binary database files (*.frm ...) from 5.0 to 4.1 doesn't work, it seem they are not compatible. Moving binary files between versions is generally a bad idea, use mysqldump instead. It creates a sql file you can run against the 4.1 server and should move all the chars over ok. E.g. if your database was called foodb then locally run: $ mysqldump -u amir -p foodb foodb.sql Then load this file into the server: $ mysql --host=server.name -u amir -p foodb foodb.sql (Or you could copy the dump file up to the server and then run the commmand locally.) Note the above will create all the tables and overwrite any existing tables and data with the new set. http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html mark -- MARK ADDISON WEB DEVELOPER 200 GRAY'S INN ROAD LONDON WC1X 8XZ UNITED KINGDOM T +44 (0)20 7430 4678 F E [EMAIL PROTECTED] WWW.ITN.CO.UK Please Note: Any views or opinions are solely those of the author and do not necessarily represent those of Independent Television News Limited unless specifically stated. This email and any files attached are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify [EMAIL PROTECTED] Please note that to ensure regulatory compliance and for the protection of our clients and business, we may monitor and read messages sent to and from our systems. Thank You. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Backup problem from 5.0 to mysql 4.1
-Original Message- From: Addison, Mark [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 18, 2006 1:22 PM To: Amir Bukhari; mysql@lists.mysql.com Subject: RE: Backup problem from 5.0 to mysql 4.1 From: Amir Bukhari Sent: 18 July 2006 09:23 I have local mysql 5.0 and I have developed an arabic site. The database encoding is utf8-bin. Localy everything work fine, all arabic text are displayed OK. Now I want to move it to a server in internet. The server has mysql 4.1 and as I restored the database there, some special arabic character are not displayed correctly. I don't know why only some character are inserted differently from others. Localy I have also tried to have both mysql server 4.1 5.0 to play with the backup and store, but without success, always the same result. Moving the binary database files (*.frm ...) from 5.0 to 4.1 doesn't work, it seem they are not compatible. Moving binary files between versions is generally a bad idea, use mysqldump instead. It creates a sql file you can run against the 4.1 server and should move all the chars over ok. E.g. if your database was called foodb then locally run: $ mysqldump -u amir -p foodb foodb.sql Then load this file into the server: $ mysql --host=server.name -u amir -p foodb foodb.sql I have tried this also, but this produce those bad character. I have used exactly what you have done above. When restoring the database which was backuped using mysqldump into mysql 5.0 everything is OK, but when restoring it to mysql 4.1 then there is those bad characters. I have also tried to backup and restore with both version of mysql mysqldump included in 5.0 and 4.1, but without success. -Amir -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Backup problem from 5.0 to mysql 4.1
Amir Bukhari wrote: -Original Message- From: Addison, Mark [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 18, 2006 1:22 PM To: Amir Bukhari; mysql@lists.mysql.com Subject: RE: Backup problem from 5.0 to mysql 4.1 From: Amir Bukhari Sent: 18 July 2006 09:23 I have local mysql 5.0 and I have developed an arabic site. The database encoding is utf8-bin. Localy everything work fine, all arabic text are displayed OK. Now I want to move it to a server in internet. The server has mysql 4.1 and as I restored the database there, some special arabic character are not displayed correctly. I don't know why only some character are inserted differently from others. Localy I have also tried to have both mysql server 4.1 5.0 to play with the backup and store, but without success, always the same result. Moving the binary database files (*.frm ...) from 5.0 to 4.1 doesn't work, it seem they are not compatible. Moving binary files between versions is generally a bad idea, use mysqldump instead. It creates a sql file you can run against the 4.1 server and should move all the chars over ok. E.g. if your database was called foodb then locally run: $ mysqldump -u amir -p foodb foodb.sql Then load this file into the server: $ mysql --host=server.name -u amir -p foodb foodb.sql I have tried this also, but this produce those bad character. I have used exactly what you have done above. When restoring the database which was backuped using mysqldump into mysql 5.0 everything is OK, but when restoring it to mysql 4.1 then there is those bad characters. I have also tried to backup and restore with both version of mysql mysqldump included in 5.0 and 4.1, but without success. There is a special commandline option for the mysqldump included in 5.0 to produce dumps suitable for 4.1. Try that. Bye Racke -- LinuXia Systems = http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP = http://www.icdevgroup.org/ Interchange Development Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Database backup Problem
I recently migrated all of our mysql databases from 4.1.X to 5.0.X. Everything is working properly except my backups. Here is the command that I am using: mysqldump -u user -ppassword --opt -A -F --delete-master-logs | gzip $BACKUPFILE`date +%m%d%y`.sql.gz This worked on the old database server, but now I'm getting the following error: mysqldump: mysqldump: Couldn't execute 'RESET MASTER': Binlog closed, cannot RESET MASTER (1186) Any insight on what I'm doing wrong would be great! Thanks, Cody -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Database backup Problem
Just checking if this user has RELOAD PRIVILEGES, as it is needed for the --master-data option which is automatically enabled with --delete-master-logs , does the error duplicate on subsequent attempts ?? Kishore Jalleda http://kjalleda.googlepages.com/projects On 3/31/06, Cody Holland [EMAIL PROTECTED] wrote: I recently migrated all of our mysql databases from 4.1.X to 5.0.X. Everything is working properly except my backups. Here is the command that I am using: mysqldump -u user -ppassword --opt -A -F --delete-master-logs | gzip $BACKUPFILE`date +%m%d%y`.sql.gz This worked on the old database server, but now I'm getting the following error: mysqldump: mysqldump: Couldn't execute 'RESET MASTER': Binlog closed, cannot RESET MASTER (1186) Any insight on what I'm doing wrong would be great! Thanks, Cody -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
restoring backup, problem with BLOB?
Hello List, I am restoring a MySQL backup (about 40MB), and its taking well over 2 hours to restore. the area where its really hanging is when its importing the BLOB There are about 1200 records, totaling about 10mb in size for these blobs. I am running MyISAM, my current memory settings read: bulk_insert_buffer_size 805306368 innodb_additional_mem_pool_size 7340032 innodb_buffer_pool_awe_mem_mb 0 innodb_buffer_pool_size 318767104 innodb_log_buffer_size 4194304 join_buffer_size131072 key_buffer_size 164626432 myisam_sort_buffer_size 193986560 net_buffer_length 16384 read_buffer_size61440 read_rnd_buffer_size258048 sort_buffer_size262136 Any ideas whats going on here? its a 3 ghz P4, running 1024 ram.
Re: Backup problem
At 12:27 AM 10/7/2004, you wrote: This is what I need to do, what is the best approach for doing this? I need to take backup of few tables in mysql, then I need to drop that entire DB, recreate it, (and sth else that's not relevant here) and then restore these backed up tables. This backup and restoring should be as fast as possible. How can I do this? Here's a few ideas. I'm sure there are more ways to do it. 1) MyISAM or InnoDb? Which version? How many rows in the tables? 2) Is the backup database accessible on the network? If so why not just create the backup database tables on the fly using something like: use bu_database; lock tables old_database.table1, ... old_database.tablen; flush tables old_database.table1, ..., old_database.tablen; create table1 like old_database.table1; insert into table1 select * from old_database.table1; create tablen like old_database.tablen; insert into tablen select * from old_database.tablen; compare the table row counts from both databases to make sure all rows were transferred. Then if ok, drop the old_database. If the table has a lot of indexes, a faster method would be to not define the indexes until later and just do a use bu_database; create table1 select * from old_database.table1; alter table1 add index ..., add index ..., add index. /*build all indexes with 1 statement*/ Of course you need to know what the old index structure was for the Alter Table command. Keep in mind that an Alter Table will create a copy of the table while it is building the indexes. I'm not sure why it has to do this when building indexes, but it does. (Unless they've changed it in 4.1 and if so someone can jump in and correct me if I'm wrong.) 3) If the backup database is not accessible on the network then you will need to do a MySQLDump (or MySQLHotCopy for ISAM/MyISAM tables) and transport the file over to the new machine and run the script there. You will then have to check the row counts manually before dropping the old database. This is usually the preferred method for large tables (several million rows). Mike -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Backup problem
This is what I need to do, what is the best approach for doing this? I need to take backup of few tables in mysql, then I need to drop that entire DB, recreate it, (and sth else that's not relevant here) and then restore these backed up tables. This backup and restoring should be as fast as possible. How can I do this? TIA, - Manish -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysql backup problem
Hi all ! I have two systems. one with mysql-version: 3.23.37 other with mysql-version: 3.23.58 now i want to take the backup of 3.23.37 data and copy to 3.23.58 ... i know i can take backup using mysqldump command ... and then copy using mysql commands but as mysql create folder for each database . is it possible to copy the particular folder(database) to 3.23.58 and then running it smoothly ... Any body got any idea ??? Please help me out.. Thanks in advance Binay
Re: Mysql backup problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Binay -- Saw your post over in php-general but it's better over here :-) ...and then Binay said... % % Hi all ! Hi! % % I have two systems. % one with mysql-version: 3.23.37 % other with mysql-version: 3.23.58 OK. % % now i want to take the backup of 3.23.37 data and copy to 3.23.58 ... % % i know i can take backup using mysqldump command ... and then copy using mysql commands I don't know about copy using mysql commands but I would definitely agree that mysqldump will work for you. % % but as mysql create folder for each database . % is it possible to copy the particular folder(database) to 3.23.58 and then running it smoothly ... Probably. Back up your .58 system, try it, and see! % % Any body got any idea ??? % % Please help me out.. % % Thanks in advance % % Binay HTH HAND :-D - -- David T-G * There is too much animal courage in (play) [EMAIL PROTECTED] * society and not sufficient moral courage. (work) [EMAIL PROTECTED] -- Mary Baker Eddy, Science and Health http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE/xzw1Gb7uCXufRwARAqdSAKDDrQSaDzn1PO0LF5JEiHIw8mX6mwCgm889 oAy5z9tGBMVIlFvdcO5vJHE= =bCwO -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Backup problem - disaster waiting to happen
I use mysqldump to dump my databases to file. I then write these files to tape. I was doing a test restore to a test server this weekend and found that for my largest database, I cannot restore from this file. I use mysql backup.script. It runs for a long time and creates most of the tables, but eventually comes up with a syntax error and stops processing the file. I have two questions: How do I get around this ? The error message is: .ERROR 1064 at line 78631: You have an error in your SQL syn s:v=\urn:schemas-microsoft-com:vml\\r\nxmlns:o=\u This data is xml data stored in one of the fields. If mysqldump created the syntax surely it should process back in correctly ? There's no way I can edit 2GB of incorrect entries in order to correct them. Secondly, how can I make the restore more fault tolerant ? If one call fails to continue with the next one ? Thank Ciao Herbert signature.asc Description: This is a digitally signed message part
Re: Backup problem - disaster waiting to happen
Hi Herbert, the -f/--force option lets you continue with the next command Thats my $0.0.2. Best regards Nils Valentin Tokyo/Japan 2003 7 28 17:57H M Kunzmann : I use mysqldump to dump my databases to file. I then write these files to tape. I was doing a test restore to a test server this weekend and found that for my largest database, I cannot restore from this file. I use mysql backup.script. It runs for a long time and creates most of the tables, but eventually comes up with a syntax error and stops processing the file. I have two questions: How do I get around this ? The error message is: .ERROR 1064 at line 78631: You have an error in your SQL syn s:v=\urn:schemas-microsoft-com:vml\\r\nxmlns:o=\u This data is xml data stored in one of the fields. If mysqldump created the syntax surely it should process back in correctly ? There's no way I can edit 2GB of incorrect entries in order to correct them. Secondly, how can I make the restore more fault tolerant ? If one call fails to continue with the next one ? Thank Ciao Herbert -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Backup problem - disaster waiting to happen
I use mysqldump to dump my databases to file. I then write these files to tape. I was doing a test restore to a test server this weekend and found that for my largest database, I cannot restore from this file. I use mysql backup.script It runs for a long time and creates most of the tables, but eventually comes up with a syntax error and stops processing the file. I have two questions: How do I get around this ? The error message is: ERROR 1064 at line 78631: You have an error in your SQL syntax. Check the manual that c om:vml\\r\nxmlns:o=\u This data is xml data stored in one of the fields. If mysqldump created the syntax surely it should process back in correctly ? There's no way I can edit 2GB of incorrect entries in order to correct them. Secondly, how can I make the restore more fault tolerant ? If one call fails to continue with the next one ? Thank Ciao Herbert -- Herbert Michael Kunzmann Binary Chaos Magician signature.asc Description: This is a digitally signed message part
Re: Backup problem - disaster waiting to happen
H M Kunzmann wrote:
I use mysqldump to dump my databases to file.
I then write these files to tape.
I was doing a test restore to a test server this weekend and found that
for my largest database, I cannot restore from this file.
I use mysql backup.script
It runs for a long time and creates most of the tables, but eventually
comes up with a syntax error and stops processing the file.
I have two questions:
How do I get around this ? The error message is:
ERROR 1064 at line 78631: You have an error in your SQL syntax. Check the manual
that c
om:vml\\r\nxmlns:o=\u
This data is xml data stored in one of the fields. If mysqldump created
the syntax surely it should process back in correctly ? There's no way I
can edit 2GB of incorrect entries in order to correct them.
Secondly, how can I make the restore more fault tolerant ? If one call
fails to continue with the next one ?
Thank
Ciao
Herbert
--
Herbert Michael Kunzmann
Binary Chaos Magician
Herbert,
It might be better if you do a per table export instead of whole
database export. If you still have files that are too large to easily
edit, use a utility like split to break them up. Below is the script we
use to backup all of our tables except for 100_PATS and 400_PATS as
those tables are dropped and reloaded everynight anyway.
Hope this helps!
walt
#!/bin/bash
cd /var/lib/mysql/NEA/
FILES=`ls *.frm`
for file in $FILES; do
LEN=${#file}
STRIP=$((LEN -4))
table=`expr substr $file 1 $STRIP`
if [ $table != 100_PATS ] [ $table != 400_PATS ]; then
/usr/bin/mysqldump -qt -u nea NEA $table -r /opt/db_dump/$table
fi
done
exit 0
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
The MySQL Backup problem
Hi, I am developing a mySql Backup software and I intend to develop two different options for backup: Complete and Incremental, where Complete means the full copy of a database, and Incremental means that only the log file have to be copied. The logic is the follow: Once a week, my customers will make a complete copy of their databases to a DAT streamer or other media they can choose, and every day they will make an incremental copy of their databases. In case of database damage, they will be able to restore the full copy they had made and run the log file in their hard disk. But, if the log file was not found, then the backed up log will be used to restore the database as closed to its last state as it could be restored. The main problem I am experiencing is that mySql is not able to make different log files for each database. This way I am obliged to copy all the databases every time I start a backup, because if the user had to use the restore option, only one single log will be executed, and it has the SQL statements used in all the databases in my server. I really would like that mySql had an option to make different log files for each database. Is it possible to be developed for the mySql team? And how long will it take you to come out this feature? Thanks in advance, P.S.: I intend to make this software and its source code available for free. Then I expect you could download and enjoy it when it was ready. sql,query - ++ Dyego Souza do Carmo ++ Dep. Desenvolvimento - E S C R I B A I N F O R M A T I C A - The only stupid question is the unasked one (somewhere in Linux's HowTo) Linux registred user : #230601 --ICQ : 221602060 $ look into my eyes Phone : +55 041 296-2311 r.112 look: cannot open my eyes Fax : +55 041 296-6640 - Reply: [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: The MySQL Backup problem
At 16:11 -0300 3/19/03, Dyego Souza do Carmo wrote: Hi, I am developing a mySql Backup software and I intend to develop two different options for backup: Complete and Incremental, where Complete means the full copy of a database, and Incremental means that only the log file have to be copied. The logic is the follow: Once a week, my customers will make a complete copy of their databases to a DAT streamer or other media they can choose, and every day they will make an incremental copy of their databases. In case of database damage, they will be able to restore the full copy they had made and run the log file in their hard disk. But, if the log file was not found, then the backed up log will be used to restore the database as closed to its last state as it could be restored. The main problem I am experiencing is that mySql is not able to make different log files for each database. This way I am obliged to copy all the databases every time I start a backup, because if the user had to use the restore option, only one single log will be executed, and it has the SQL statements used in all the databases in my server. I really would like that mySql had an option to make different log files for each database. Is it possible to be developed for the mySql team? And how long will it take you to come out this feature? Perhaps you could use the --database option to mysqlbinlog to generate per-database logs. -- Paul DuBois http://www.kitebird.com/ sql, query - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
backup-problem
hallo! i have a backup-problem: when i use mysqldump -u michael -p --opt --all-databases backup i get the following error: USE backup; mysqldump: Got error: 1017: Can't find file: 'title.MYD' (errno: 2) when using LOCK TABLES but when i use mysqldump -u michael -p --opt --database books backup it works. table title is a part of books why? what is going wrong? -- Gruß bye Michael Ott - - Siemens AG - IS IT PS 51 ERL - - Werner-von-Siemens-Strasse 60 - - 91050 Erlangen- - Tel. +49 91 31 7 42 0 54 - - [EMAIL PROTECTED] - - open-source and you have much fun - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
