mysqldump --opt crashes server on InnoDB tables

2004-09-24 Thread Thomas Plümpe
Hi there, I'm using mysql on a Mandrake 9.2 server. As I wanted to move to InnoDB tables and the standard mysql-4.0.15 on Mandrake doesn't have that compiled in, I obtained the most recent (4.0.21) version from mysql.com, uninstalled the Mandrake version and installed the mysql.com one. I assumed

Re: Table corruption results after using "mysqldump --opt"

2003-12-01 Thread Chris Waskowich
On Dec 01, 2003, at 18:00, Jared Klett wrote: b.) Is there a proven way to backup MySQL databases that have to be up and running 24/7/365? Well, I don't know so much about a 'proven' way - but I use replication on another server and it works pretty good for me. When i want to make a static bac

Table corruption results after using "mysqldump --opt"

2003-12-01 Thread Jared Klett
hi all, I have MySQL 3.23.58 running on Solaris 9 x86, and it's been working fantastically. I recently added this to a crontab: /usr/local/mysql/bin/mysqldump --all-databases --opt -u jklett > /storage/backup/mysql-all-databases.sql 2>&1 And the backup file gets created with the right amou

mysqldump --opt

2001-04-03 Thread Mark Lo
Hi, As I know, mysqldump --opt command will lock all the tables at once. I got confused from the above statement. What I have been confused is that if I have three databases. And I am trying to backup all three databases, using mysqldump --opt database1 > /xxx/datatbase1.sql ...