Re: General Question on Upgrading
søndag 04. januar 2004, 22:45, skrev [EMAIL PROTECTED]: I got version 3.23.56 of mysql with my redhat installation as an rpm package and now want to upgrade to the latest 4 version. My question is: how I can upgrade my current installation myself without going through the rpm package installer? Thanks, -Jalil I guess you can install the tarball in /usr/local. You will then have a directory called something like mysql-standard-4.0.17-pc-linux-i686. Make a symlink to it call mysql so you will have /usr/local/mysql Inside that directory remove the data directory, and make a symlink called data to the directory where you have your databases for the old installation. When the new database is up and running you need to run mysql_fix_privilege_tables since there has been some changes since 3.23 This is a *very* rough description that may not suit you setup, but it should give you some ideas. See the README and INSTALL-BINARY files in the tarball. Regards, Arne -- Arne K. Haaje | www.drlinux.no Bregneveien 9 | 1825 Tomter | M: 92 88 44 66 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: dropping multiple tables with one command question
fredag 02. januar 2004, 12:11, skrev Egor Egorov: tom poe [EMAIL PROTECTED] wrote: What's the command for dropping multiple tables? Example: 12 tables that all start with: phpbb_ What? Well, the install isn't going as planned. I am having to reinstall as I try to work out script path (I think) or some other piece of info that isn't entered correctly, yet. Anyway, DROP TABLE tablename; is one table. I want to drop all the tables without typing them, but using DROP TABLE phpbb*; doesn't work. You can't use wildcards in the DROP TABLE command. But you can do DROP table1; DROP table2; DROP table3; etc.. Arne -- Arne K. Haaje | www.drlinux.no Bregneveien 9 | 1825 Tomter | M: 92 88 44 66 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Sporadic myisam table corruption.
torsdag 18. desember 2003, 13:24, skrev Victor Medina: I also agree with you, it might be a hardware problem, but i also must note, that in a environment with very often writes to the db, myisam tables are not always the best choice, that's why i suggested a change to InnoDB tables, a problem with sql or logic is more likely to happen that a hardware glitch I frequently got corruption on a 3GB tablefile when running out of memory. Installing more memory solved the problem. Arne -- Arne K. Haaje | www.drlinux.no Bregneveien 9 | 1825 Tomter | M: 92 88 44 66 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Dead server
Hello, After upgrading to 4.0.4 from 4.0.2 on three server we have got some mysterious problems with one of the server. Several times it appears to be dead. Connecting takes a very long time, and the CPU load goes throug the roof and beyond. The two other servers runs without problems. The only difference between the servers is that the one with problems is a master for the two others (replicating one DB), and the machine is dual CPU. All serveres run Linux. When the problem occurs I have tailed the slow-log. This crops up every time when there is a problem. I have no idea what it is! # administrator command: Statistics; # User@Host: xxx # Query_time: 31 Lock_time: 0 Rows_sent: 0 Rows_examined: 0 # administrator command: Statistics; # User@Host: xxx # Query_time: 32 Lock_time: 0 Rows_sent: 1 Rows_examined: 70 # administrator command: Statistics; # User@Host: xxx # Query_time: 33 Lock_time: 0 Rows_sent: 0 Rows_examined: 0 I think this statistics command may be what is causing the problems, so can anybody tell me what is happening? Regards, Arne -- Arne K. Haaje | T: 69 92 04 90 Bregneveien 9 | F: 69 92 04 91 1825 Tomter | M: 92 88 44 66 http://www.drlinux.no/ - 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: 'too many connections'
Christopher Book wrote: No, I'm not using mysql_pconnect, and my apache configuration seems fine. I don't have very many users at the moment so there is no reason for the connections filling up. This can be due to your apache configuration. do you use mysql_pconnect function in php. Check you apache setting agains MaxClients StartServers and etc... Try adding something like set-variable=wait_timeout=1800 to your my.cnf. We found that when using mysql_pconnect the connections stuck around for far to long. MySQL's default is pretty high for a webserver that gets a few hits. After adding wait_timeout=1800 we have never seen 'too many connections' again. We still use mysql_pconnect. Regards, Arne -- Arne K. Haaje | T: 69 92 04 90 Enebakkveien 2 | F: 69 92 04 91 1625 Tomter | M: 92 88 44 66 - 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
Replicating from 3.23.42 to 4.0 - problem
Can I replicate a 3.23.42 database to a 4.0.0 server? I have not seen mentioned any place that you can not so I tried.. The error log on the slave say; 011108 15:54:17 Slave: connected to master 'user@master:32354', replication started in log 'FIRST' at position 4 011108 15:54:17 Could not parse log event entry, check the master for binlog corruption This may also be a network problem, or just a bug in the master or slave code. 011108 15:54:17 Error running query, slave aborted. Fix the problem, and re-start the slave thread with mysqladmin start-slave. We stopped at log 'FIRST' position 4 011108 15:54:17 Slave thread exiting, replication stopped in log 'FIRST' at position 4 I have tried SQL_SLAVE_SKIP_COUNTER=2; SLAVE START; as suggested in the manual, but without luck. I have also tried taking a new snapshot. BTW, the master is also replicated to another slave running 3.23.42. This works fine, so the master seems OK. All three servers are running on Slackware Linux 8. Regards, Arne K. Haaje - 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
