Re: moving from 3.23.58 to 5.0.45
On Thu, Oct 30, 2008 at 5:16 AM, Obantec Support [EMAIL PROTECTED]wrote: Hi are there any doc's on how to migrate DB in 3.23.58 format to 5.0.45 moving from a Fedora Core3 to Centos5.2 server. Mark http://www.justfuckinggoogleit.com/?q=mysql+upgrade First result. -- Rob Wultsch
moving from 3.23.58 to 5.0.45
Hi are there any doc's on how to migrate DB in 3.23.58 format to 5.0.45 moving from a Fedora Core3 to Centos5.2 server. Mark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: moving from 3.23.58 to 5.0.45
Hi Mark, from my experience I can tell you that you can easily migrate. A quick and dirty way is to use the two(or more) different MySQL installations on same server (or even different ones) and different ports of course. You dump the whole DB from the 3.23.58 and import it on the 5.0.45. If you have problems try with 4.1 or 4.0 as a midway step. At this very moment I can't tell you if you will have problems with the 'big' jump, but you should test with a smaller set of data(if your DB is huge) and after that decide if do the direct jump or use a step in the middle. Here's the idea: [3.23.58]---[5.0.45] OR [3.23.58]---[4.x]---[5.0.45] OR [3.23.58]---[4.0.x]---[4.1.x]---[5.0.45] Commands to use: [3.23.58]# mysqldump --all-databases dump.sql will do the job and [5.0.45] mysql source dump.sql will complete the opera! remember that after that also the grant tables will be replaced from the original DB(3.23.58) hope it helps Claudio 2008/10/30 Obantec Support [EMAIL PROTECTED] Hi are there any doc's on how to migrate DB in 3.23.58 format to 5.0.45 moving from a Fedora Core3 to Centos5.2 server. Mark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
Re: moving from 3.23.58 to 5.0.45
On thing that tripped me up when I did the same move was the change in LEFT JOIN syntax. It now joins to the LAST table in a list. This change actually happened half way through the 4.0x series. Doesn't effect data, but does effect queries. There MAY also be a difference on how string comparisons occur. I've had to add 'RTRIM' when comparing CHAR type with strings from the web which are not space extended, but that may just be my vesion of DBD::mysql.Good luck. On Thu, October 30, 2008 05:29, Claudio Nanni wrote: Hi Mark, from my experience I can tell you that you can easily migrate. A quick and dirty way is to use the two(or more) different MySQL installations on same server (or even different ones) and different ports of course. You dump the whole DB from the 3.23.58 and import it on the 5.0.45. If you have problems try with 4.1 or 4.0 as a midway step. At this very moment I can't tell you if you will have problems with the 'big' jump, but you should test with a smaller set of data(if your DB is huge) and after that decide if do the direct jump or use a step in the middle. Here's the idea: [3.23.58]---[5.0.45] OR [3.23.58]---[4.x]---[5.0.45] OR [3.23.58]---[4.0.x]---[4.1.x]---[5.0.45] Commands to use: [3.23.58]# mysqldump --all-databases dump.sql will do the job and [5.0.45] mysql source dump.sql will complete the opera! remember that after that also the grant tables will be replaced from the original DB(3.23.58) hope it helps Claudio 2008/10/30 Obantec Support [EMAIL PROTECTED] Hi are there any doc's on how to migrate DB in 3.23.58 format to 5.0.45 moving from a Fedora Core3 to Centos5.2 server. Mark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql dump problems, no data dumped
Hi, Im having an issue using mysqldump to dump a DB from comercial app which includes mysql 4.0.18-pro. It doesnt however include mysql dump for online backups so Im using the one installed by default in my linux dist which as you can see below is version 10.11. My problem is that the dump is exiting with exist status 0 but Im not getting any of the data dumped. The WHOLE dump is shown in text below: -- MySQL dump 10.11 -- -- Host: localhostDatabase: OpManagerDB -- -- -- Server version 4.0.18-pro /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; /*!40103 SET [EMAIL PROTECTED] */; /*!40101 SET [EMAIL PROTECTED] */; /*!40014 SET [EMAIL PROTECTED] */; /*!40014 SET [EMAIL PROTECTED] */; /*!40111 SET [EMAIL PROTECTED] */; -- Dump completed on 2008-10-27 13:50:53 Can anyone help me? I need to work out why no data is written, thanks Andy.
Re: auto_increment problem
alter table tablename modify id int not null auto_increment primary key; On Sat, Oct 25, 2008 at 2:48 AM, Paul [EMAIL PROTECTED] wrote: Anybody know if there's a way to change a primary key field that is not auto-incremented, turning on auto-increment but preserving the values that are currently in it? TIA, Paul W -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
Re: mysql dump problems, no data dumped
Hi,andy. Can you show me the details about the options of mysqldump to be used ? On Fri, Oct 31, 2008 at 1:25 AM, Andy Smith [EMAIL PROTECTED] wrote: Hi, Im having an issue using mysqldump to dump a DB from comercial app which includes mysql 4.0.18-pro. It doesnt however include mysql dump for online backups so Im using the one installed by default in my linux dist which as you can see below is version 10.11. My problem is that the dump is exiting with exist status 0 but Im not getting any of the data dumped. The WHOLE dump is shown in text below: -- MySQL dump 10.11 -- -- Host: localhostDatabase: OpManagerDB -- -- -- Server version 4.0.18-pro /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; /*!40103 SET [EMAIL PROTECTED] */; /*!40101 SET [EMAIL PROTECTED] */; /*!40014 SET [EMAIL PROTECTED] */; /*!40014 SET [EMAIL PROTECTED] */; /*!40111 SET [EMAIL PROTECTED] */; -- Dump completed on 2008-10-27 13:50:53 Can anyone help me? I need to work out why no data is written, thanks Andy. -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
Re: moving from 3.23.58 to 5.0.45
I think Claudio Nanni 's suggestion is the best! On Thu, Oct 30, 2008 at 8:29 PM, Claudio Nanni [EMAIL PROTECTED]wrote: Hi Mark, from my experience I can tell you that you can easily migrate. A quick and dirty way is to use the two(or more) different MySQL installations on same server (or even different ones) and different ports of course. You dump the whole DB from the 3.23.58 and import it on the 5.0.45. If you have problems try with 4.1 or 4.0 as a midway step. At this very moment I can't tell you if you will have problems with the 'big' jump, but you should test with a smaller set of data(if your DB is huge) and after that decide if do the direct jump or use a step in the middle. Here's the idea: [3.23.58]---[5.0.45] OR [3.23.58]---[4.x]---[5.0.45] OR [3.23.58]---[4.0.x]---[4.1.x]---[5.0.45] Commands to use: [3.23.58]# mysqldump --all-databases dump.sql will do the job and [5.0.45] mysql source dump.sql will complete the opera! remember that after that also the grant tables will be replaced from the original DB(3.23.58) hope it helps Claudio 2008/10/30 Obantec Support [EMAIL PROTECTED] Hi are there any doc's on how to migrate DB in 3.23.58 format to 5.0.45 moving from a Fedora Core3 to Centos5.2 server. Mark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
Re: lost connection to mysql server during query errors
In my experiences, there're three reasons below. 1. Your network is not stable. 2. Your mysqld's parameter called max_allowed_packet is adjusted too small, trying to increase it. 3. Your mysqld's parameter called connect_timeout is adjusted too small, trying to increase it. On Thu, Oct 30, 2008 at 1:05 PM, mos [EMAIL PROTECTED] wrote: At 10:21 PM 10/29/2008, you wrote: I've never had a lot of luck tracking down this sort of problem. One thing I've found to be a good first step is to add each server involved to the other server's /etc/hosts file (and restart MySQL so it notices). Don't have much more to offer other than the usual suspects: recent versions, persistent vs. non-persistent connections, etc. A long shot would be to make sure your always talking to the same database server- if you're doing, say, DNS round-robin or load balancing or something, maybe you're getting shunted to a different db server and it's killing the connection... don't know what your setup is. Another long shot in a multi-db-server config would be to make sure they all have different server ID's. Good luck... hopefully someone else has better advice :) Jake Just a guess, but maybe it's your network card? I'm using MySQL 5.01 with MyISAM tables and my application will occasionally hang for hours in the midst of executing a simple 1 table Select statement. I usually end up killing the program. There are no processes running on the MySQL server. I think the problem was the number of connections the program created. Although there were only at most 10 simultaneous connections, my program when the query finished executing, it threw the connection away and recreated a new one for each query, and MySQL reported there were some 10k connections made to the server. I ended up using connection pooling and now the number of connections reaches a high of around 10 and I haven't had the problem since. Mike On Wed, Oct 29, 2008 at 2:47 AM, Waynn Lue [EMAIL PROTECTED] wrote: We've started seeing mysql errors in the logs, and when i look at the output of mysql_error() (in php), i get lost connection to mysql server during query. Here's an example stack trace: 'Can't connect to name database [Lost connection to MySQL server during query]' Similarly, we're seeing stack traces here as well: 'Can't connect to name database []' I usually only see this mesasge when I don't use a connection for awhile and it timeouts, but in this case, the connection is only opened for the duration of a script, which can't be running for more than a second. The mysql error logs don't show anything, and wait_timeout is set to 28800. At first, I thought it was because I was calling mysql_select_db too much, so I ended up using two mysql connections per page load, but that didn't seem to change anything. How can we prevent this error from happening, what else can I do to diagnose this further? Google brings up some more discussions about it, but nothing seems related to this, like packetsize. This is happening when we select two ids from a database. And SHOW PROCESSLIST shows that the number of connections aren't even coming close to max connections. Thanks for any advice, Waynn -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
Re: mysql dump problems, no data dumped
what command are you using to do the dump? I mean the entire command, including all the options. On Thu, Oct 30, 2008 at 12:25 PM, Andy Smith [EMAIL PROTECTED] wrote: Hi, Im having an issue using mysqldump to dump a DB from comercial app which includes mysql 4.0.18-pro. It doesnt however include mysql dump for online backups so Im using the one installed by default in my linux dist which as you can see below is version 10.11. My problem is that the dump is exiting with exist status 0 but Im not getting any of the data dumped. The WHOLE dump is shown in text below: -- MySQL dump 10.11 -- -- Host: localhostDatabase: OpManagerDB -- -- -- Server version 4.0.18-pro /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; /*!40103 SET [EMAIL PROTECTED] */; /*!40101 SET [EMAIL PROTECTED] */; /*!40014 SET [EMAIL PROTECTED] */; /*!40014 SET [EMAIL PROTECTED] */; /*!40111 SET [EMAIL PROTECTED] */; -- Dump completed on 2008-10-27 13:50:53 Can anyone help me? I need to work out why no data is written, thanks Andy. -- Jim Lyons Web developer / Database administrator http://www.weblyons.com
