Well it turned out we had table and index corruption on the master db (db01) so I've fixed it and am rebuilding db02. We're having a mgmt meeting this wed to discuss updating the production servers to MySQL ver 4.x.
The current servers run RedHat 7.1 with a single Pent-III 933mhz with 256k L2 cache and 256MB RAM. I'd like to pump the servers up to dual Pent-III 1.4ghz with 512 L2 cache and 2GB RAM, then load the latest RH OS on them and upgrade to MySQL ver 4.x. Assuming I get approval for this, what is the best way to move the current db files (ver 3.23) to the rebuilt serves running MySQL ver 4.x? Are there any compatability issues or things that need to be converted? All tables are MyISAM. Thanks, Jeff McKeon IT Manager Telaurus Communications LLC [EMAIL PROTECTED] (973) 889-8990 ex 209 ***The information contained in this communication is confidential. It is intended only for the sole use of the recipient named above and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication, or any of its contents or attachments, is expressly prohibited. If you have received this communication in error, please re-send it to the sender and delete the original message, and any copy of it, from your computer system. Thank You.*** > -----Original Message----- > From: MySQL [mailto:[EMAIL PROTECTED] > Sent: Monday, July 21, 2003 2:02 PM > To: [EMAIL PROTECTED] > Subject: Re: Slave not working.... > > > > Since you are hoping to not repeat the replication setup, > your one chance is that the slave was fully synced at the > time of the power failure. If you check the master, you will > see that it is now using a different log file (whenever > mysqld stops/starts a new log is created). You can shutdown > the slave, edit the master.info file to point to the new > logfile (there may be more than one) and cross fingers. PS. > If this is not fully understood, don't try it. > > > I had a power failure on the master and it bounced rather > ungracefully. > Now I'm getting this error on the slave and it's not > replicating. Both > are ver 3.23 > > mysql> slave start; > Query OK, 0 rows affected (0.00 sec) > > mysql> show slave status \G; > *************************** 1. row *************************** > Master_Host: 10.32.1.10 > Master_User: repli > Master_Port: 3306 > Connect_retry: 60 > Log_File: db01tc0927-bin.035 > Pos: 73 > Slave_Running: No > Replicate_do_db: > Replicate_ignore_db: > Last_errno: 1062 > Last_error: error 'Duplicate entry '245937' for key > 1' on query > '%' > Skip_counter: 0 > 1 row in set (0.00 sec) > > ERROR: > No query specified > > How do I fix this? > > Jeff McKeon > > > -- > mysql, query > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?> [EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
