Re: upgrading mysql
The issue is that in theory this should work given the facts announced by MySQL regarding binary logging and replication. I can certainly do it the way you propose, but to my mind I should also be able to do it using the fact that both machines are fully synced and hence at that point I should be able to to local respective dumps and restores and still be in sync. Anyone knows anything special about position 106? It seems to be the very initial position in MySQL 5.1 servers? mysql show master status; +---+--+--+--+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +---+--+--+--+ | X-bin.01 | 106 | | | +---+--+--+--+ 1 row in set (0.00 sec) r...@:/usr/local/mysql/data ] /usr/local/mysql/bin/mysqlbinlog mssdb2-bin.01 /*!40019 SET @@session.max_insert_delayed_threads=0*/; /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/; DELIMITER /*!*/; # at 4 #100113 13:50:40 server id 5 end_log_pos 106 Start: binlog v 4, server v 5.1.42-log created 100113 13:50:40 at startup # Warning: this binlog is either in use or was not closed properly. ROLLBACK/*!*/; BINLOG ' ABZOSw8FZgAAAGoBAAQANS4xLjQyLWxvZwAA Fk5LEzgNAAgAEgAEBAQEEgAAUwAEGggICAgC '/*!*/; DELIMITER ; # End of log file ROLLBACK /* added by mysqlbinlog */; /*!50003 SET completion_ty...@old_completion_type*/; r...@:/usr/local/mysql/data ] ~Lawrence Tom Worster wrote: Frankly, I didn't entirely understand what you were proposing. I got lost around step 6. Is the issue total time for the procedure or service downtime? On 1/12/10 12:58 PM, Lawrence Sorrillo sorri...@jlab.org wrote: This is two upgrades done in sequence(the reload takes about three hours per machine) . I can do what I am proposing in parallel. Do you see it as problematic? ~Lawrence Tom Worster wrote: How about: 1 shut down the slave, upgrade it, restart it, let it catch up. 2 shut down the master, upgrade it, restart it, let the slave catch up. ? On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. 2. Ensure that replication on the slave is caught up to the last change on the master. 3. stop binary logging on the master. 4. stop replication on the slave. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. 8. After loading slave, test then start slave (get configs in place and restart server). I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. Comments? ~Lawrence -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgrading mysql
On 1/13/10 2:28 PM, Lawrence Sorrillo sorri...@jlab.org wrote: The issue is that in theory this should work given the facts announced by MySQL regarding binary logging and replication. I can certainly do it the way you propose, but to my mind I should also be able to do it using the fact that both machines are fully synced and hence at that point I should be able to to local respective dumps and restores and still be in sync. i can't point at anything in your recipe and say that it doesn't work. it might work. i'd be nervous that something in steps 5 and 6 might involve a change on the master that needs to be replicated. since your using a dump and not a binary copy of myisam file, i suppose this ought to be safe. but i would be nervous all the same. on the other hand, i do know that the recipe i gave works because i've used it often. it also has the virtue of no need for recording binlog file names and position etc etc. plus it's the procedure recommended by the mysql folk themselves, which is worth something to me. the other thing i've done is: initial status: A is the master and B is the slave. service is operating off the master. 1 stop B, upgrade it, restart it, let it catch up. 2 stop service and then stop A 3 change B's conf file to make it the master. restart it 4 resume service using B 5 upgrade A and bring it online as a slave this has the virtue of very short service outage. with some rehearsal, it isn't beyond my skills. Anyone knows anything special about position 106? It seems to be the very initial position in MySQL 5.1 servers? the manual says: If the master has been running previously without binary logging enabled, the log name and position values displayed by SHOW MASTER STATUS or mysqldump --master-data will be empty. In that case, the values that you need to use later when specifying the slave's log file and position are the empty string ('') and 4. perhaps you have an init-file that advances it to position 106? mysql show master status; +---+--+--+--+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +---+--+--+--+ | X-bin.01 | 106 | | | +---+--+--+--+ 1 row in set (0.00 sec) r...@:/usr/local/mysql/data ] /usr/local/mysql/bin/mysqlbinlog mssdb2-bin.01 /*!40019 SET @@session.max_insert_delayed_threads=0*/; /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/; DELIMITER /*!*/; # at 4 #100113 13:50:40 server id 5 end_log_pos 106 Start: binlog v 4, server v 5.1.42-log created 100113 13:50:40 at startup # Warning: this binlog is either in use or was not closed properly. ROLLBACK/*!*/; BINLOG ' ABZOSw8FZgAAAGoBAAQANS4xLjQyLWxvZwAA Fk5LEzgNAAgAEgAEBAQEEgAAUwAEGggICAgC '/*!*/; DELIMITER ; # End of log file ROLLBACK /* added by mysqlbinlog */; /*!50003 SET completion_ty...@old_completion_type*/; r...@:/usr/local/mysql/data ] ~Lawrence Tom Worster wrote: Frankly, I didn't entirely understand what you were proposing. I got lost around step 6. Is the issue total time for the procedure or service downtime? On 1/12/10 12:58 PM, Lawrence Sorrillo sorri...@jlab.org wrote: This is two upgrades done in sequence(the reload takes about three hours per machine) . I can do what I am proposing in parallel. Do you see it as problematic? ~Lawrence Tom Worster wrote: How about: 1 shut down the slave, upgrade it, restart it, let it catch up. 2 shut down the master, upgrade it, restart it, let the slave catch up. ? On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. 2. Ensure that replication on the slave is caught up to the last change on the master. 3. stop binary logging on the master. 4. stop replication on the slave. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. 8. After loading slave, test then start slave (get configs in place and restart server). I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. Comments? ~Lawrence
Re: upgrading mysql
On Jan 13, 2010, at 1:28 PM, Lawrence Sorrillo wrote: The issue is that in theory this should work given the facts announced by MySQL regarding binary logging and replication. I can certainly do it the way you propose, but to my mind I should also be able to do it using the fact that both machines are fully synced and hence at that point I should be able to to local respective dumps and restores and still be in sync. Anyone knows anything special about position 106? It seems to be the very initial position in MySQL 5.1 servers? It's not. 4 is still the initial position, as shown by the at 4 in your mysqlbinlog output below. The 106 that you observe is the position *after* the server writes the initial event to the binary log. It writes this event immediately after opening the file, even before executing any statements. If you want the gory details: This event is the format description event that identifies in the binary log file the server version and other information. See http://forge.mysql.com/wiki/MySQL_Internals_Binary_Log#Binary_Log_Versions if you have a high tolerance for pain. :-) mysql show master status; +---+--+--+--+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +---+--+--+--+ | X-bin.01 | 106 | | | +---+--+--+--+ 1 row in set (0.00 sec) r...@:/usr/local/mysql/data ] /usr/local/mysql/bin/mysqlbinlog mssdb2-bin.01 /*!40019 SET @@session.max_insert_delayed_threads=0*/; /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/; DELIMITER /*!*/; # at 4 #100113 13:50:40 server id 5 end_log_pos 106 Start: binlog v 4, server v 5.1.42-log created 100113 13:50:40 at startup # Warning: this binlog is either in use or was not closed properly. ROLLBACK/*!*/; BINLOG ' ABZOSw8FZgAAAGoBAAQANS4xLjQyLWxvZwAA Fk5LEzgNAAgAEgAEBAQEEgAAUwAEGggICAgC '/*!*/; DELIMITER ; # End of log file ROLLBACK /* added by mysqlbinlog */; /*!50003 SET completion_ty...@old_completion_type*/; r...@:/usr/local/mysql/data ] ~Lawrence Tom Worster wrote: Frankly, I didn't entirely understand what you were proposing. I got lost around step 6. Is the issue total time for the procedure or service downtime? On 1/12/10 12:58 PM, Lawrence Sorrillo sorri...@jlab.org wrote: This is two upgrades done in sequence(the reload takes about three hours per machine) . I can do what I am proposing in parallel. Do you see it as problematic? ~Lawrence Tom Worster wrote: How about: 1 shut down the slave, upgrade it, restart it, let it catch up. 2 shut down the master, upgrade it, restart it, let the slave catch up. ? On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. 2. Ensure that replication on the slave is caught up to the last change on the master. 3. stop binary logging on the master. 4. stop replication on the slave. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. 8. After loading slave, test then start slave (get configs in place and restart server). I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. Comments? ~Lawrence -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=paul.dub...@sun.com -- Paul DuBois Sun Microsystems / MySQL Documentation Team Madison, Wisconsin, USA www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgrading mysql
How about: 1 shut down the slave, upgrade it, restart it, let it catch up. 2 shut down the master, upgrade it, restart it, let the slave catch up. ? On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. 2. Ensure that replication on the slave is caught up to the last change on the master. 3. stop binary logging on the master. 4. stop replication on the slave. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. 8. After loading slave, test then start slave (get configs in place and restart server). I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. Comments? ~Lawrence -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: upgrading mysql
Also see http://dev.mysql.con/doc/refman/5.0/en/mysql-upgrade.html. And make sure you make a backup before you do anything :) -Original Message- From: Tom Worster [mailto:f...@thefsb.org] Sent: Tuesday, January 12, 2010 10:47 AM To: Lawrence Sorrillo; mysql@lists.mysql.com Subject: Re: upgrading mysql How about: 1 shut down the slave, upgrade it, restart it, let it catch up. 2 shut down the master, upgrade it, restart it, let the slave catch up. ? On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. 2. Ensure that replication on the slave is caught up to the last change on the master. 3. stop binary logging on the master. 4. stop replication on the slave. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. 8. After loading slave, test then start slave (get configs in place and restart server). I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. Comments? ~Lawrence -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=jgor...@westernwats.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgrading mysql
This is two upgrades done in sequence(the reload takes about three hours per machine) . I can do what I am proposing in parallel. Do you see it as problematic? ~Lawrence Tom Worster wrote: How about: 1 shut down the slave, upgrade it, restart it, let it catch up. 2 shut down the master, upgrade it, restart it, let the slave catch up. ? On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. 2. Ensure that replication on the slave is caught up to the last change on the master. 3. stop binary logging on the master. 4. stop replication on the slave. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. 8. After loading slave, test then start slave (get configs in place and restart server). I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. Comments? ~Lawrence -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgrading mysql
Lawrence Sorrillo wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. ok 2. Ensure that replication on the slave is caught up to the last change on the master. why? You are just going to replace it later. 3. stop binary logging on the master. why? You can just disconnect the slave 4. stop replication on the slave. You can do this at step 2. Just issue STOP SLAVE IO_THREAD; The SQL thread can keep moving along. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) Yes. No need to create binary logs for the rebuild. 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. There is a faster way. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. Once you have QA-ed your new 5.1 master, you can shut it down then copy the entire image (binaries and all) directly to the slave machine. This is much faster than rebuilding from a dump and it ensures that you have identical data to start replication with. After the copy, then restart the master with binary logging. 8. After loading slave, test then start slave (get configs in place and restart server). Yes, it's always good to test any server image before putting it online. The CHANGE MASTER TO command to use for the slave will be at position 4 of the first binary log created after the binary image was captured. I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. You are correct. Because you are re-imaging your slave from your master, there is no need to track binary log or relay log positions. See also: http://dev.mysql.com/doc/refman/5.1/en/replication-howto-rawdata.html ** SAFETY ADVICE ** - always ensure you have a clean binary backup of any server you want to perform major maintenance to. In the off-chance that something does happen to go wrong, you will have it available for the fastest possible restore-to-original-state -- Shawn Green, MySQL Senior Support Engineer Sun Microsystems, Inc. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgrading mysql
Hi: I want to ensure that right after the reload that the same data is present in both the master and the slave. They are in perfect sync. Then I think its safe to consider starting binary logging and replication etc. And after these are started, changes can start? And in setting up replication in this manner I would not use the CHANGE MASTER... I will just master-host=xxx.xxx.xxx.xxx master-connect-retry=60 master-user=auser master-password=apassword in the my.cnf file and restart the slave server. From there it should start reading the binary logs and committing changes properly. Is this correct? ~Lawrence Shawn Green wrote: Lawrence Sorrillo wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. ok 2. Ensure that replication on the slave is caught up to the last change on the master. why? You are just going to replace it later. 3. stop binary logging on the master. why? You can just disconnect the slave 4. stop replication on the slave. You can do this at step 2. Just issue STOP SLAVE IO_THREAD; The SQL thread can keep moving along. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) Yes. No need to create binary logs for the rebuild. 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. There is a faster way. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. Once you have QA-ed your new 5.1 master, you can shut it down then copy the entire image (binaries and all) directly to the slave machine. This is much faster than rebuilding from a dump and it ensures that you have identical data to start replication with. After the copy, then restart the master with binary logging. 8. After loading slave, test then start slave (get configs in place and restart server). Yes, it's always good to test any server image before putting it online. The CHANGE MASTER TO command to use for the slave will be at position 4 of the first binary log created after the binary image was captured. I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. You are correct. Because you are re-imaging your slave from your master, there is no need to track binary log or relay log positions. See also: http://dev.mysql.com/doc/refman/5.1/en/replication-howto-rawdata.html ** SAFETY ADVICE ** - always ensure you have a clean binary backup of any server you want to perform major maintenance to. In the off-chance that something does happen to go wrong, you will have it available for the fastest possible restore-to-original-state -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgrading mysql
On Jan 12, 2010, at 12:36 PM, Lawrence Sorrillo wrote: Hi: I want to ensure that right after the reload that the same data is present in both the master and the slave. They are in perfect sync. Then I think its safe to consider starting binary logging and replication etc. And after these are started, changes can start? And in setting up replication in this manner I would not use the CHANGE MASTER... I will just master-host=xxx.xxx.xxx.xxx master-connect-retry=60 master-user=auser master-password=apassword in the my.cnf file and restart the slave server. From there it should start reading the binary logs and committing changes properly. Is this correct? You're upgrading to MySQL 5.1, for which several of those options no longer have any effect. Better to use CHANGE MASTER. See: http://dev.mysql.com/doc/refman/5.1/en/replication-options-slave.html http://dev.mysql.com/doc/refman/5.1/en/news-5-1-17.html -- Paul DuBois Sun Microsystems / MySQL Documentation Team Madison, Wisconsin, USA www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgrading mysql
Frankly, I didn't entirely understand what you were proposing. I got lost around step 6. Is the issue total time for the procedure or service downtime? On 1/12/10 12:58 PM, Lawrence Sorrillo sorri...@jlab.org wrote: This is two upgrades done in sequence(the reload takes about three hours per machine) . I can do what I am proposing in parallel. Do you see it as problematic? ~Lawrence Tom Worster wrote: How about: 1 shut down the slave, upgrade it, restart it, let it catch up. 2 shut down the master, upgrade it, restart it, let the slave catch up. ? On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. 2. Ensure that replication on the slave is caught up to the last change on the master. 3. stop binary logging on the master. 4. stop replication on the slave. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. 8. After loading slave, test then start slave (get configs in place and restart server). I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. Comments? ~Lawrence -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: upgrading mysql
Hi, The step 6 in simple terms is Here we need to build two server ( both master and slave ). Instead of building two server as it takes double the time of building in one server. After building an server, make a copy of the first server files at OS level and copy it to the server and start the same. Configure the replication between the two server. By doing this, We will save the import time in second server. Thanks Suresh Kuna MySQL DBA On Wed, Jan 13, 2010 at 3:58 AM, Tom Worster f...@thefsb.org wrote: Frankly, I didn't entirely understand what you were proposing. I got lost around step 6. Is the issue total time for the procedure or service downtime? On 1/12/10 12:58 PM, Lawrence Sorrillo sorri...@jlab.org wrote: This is two upgrades done in sequence(the reload takes about three hours per machine) . I can do what I am proposing in parallel. Do you see it as problematic? ~Lawrence Tom Worster wrote: How about: 1 shut down the slave, upgrade it, restart it, let it catch up. 2 shut down the master, upgrade it, restart it, let the slave catch up. ? On 1/12/10 12:34 PM, Lawrence Sorrillo sorri...@jlab.org wrote: Hi: I want to upgrade a master and slave server from mysql 4.1 to mysql 5.1. I want to so something like follows: 1. Stop all write access to the master server. 2. Ensure that replication on the slave is caught up to the last change on the master. 3. stop binary logging on the master. 4. stop replication on the slave. 5. dump the master, stop old 4.1 server, start new 5.1 server and reload master dump file under 5.1 server ( binary logging is turned off) 6. dump the slave, stop old 4.1 server, start new 5.1 server and reload slave dump file under 5.1 server. 7. After loading is complete, test then start binary logging on master while still preventing updates to updates. 8. After loading slave, test then start slave (get configs in place and restart server). I am thinking that in this scenario I dont have to bother with recording binlog file names and position etc etc. That both servers will have the same databases abd replication and binary logging will start on the two databases with no data loss and continue forward. Comments? ~Lawrence -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=sureshkumar...@gmail.com -- Thanks Suresh Kuna MySQL DBA
Re: Upgrading MySQL from 5.0 to 5.1
What I always did since 3.23 upwards is new installation and import. My tecnique allows me to install as many mysql instances as I want, I always use specific user, homedir, datadir, my.cnf, for each installation. In this way I can have theoretically unlimited number of mysql instances on one host. In your case I would install the new 5.1 in a custom home (e.g. /home/mysql5123) use your previous my.cnf from the 5.0 installation to get all previous settings and make it use the same datadir. To force one installation to use ONE AND ONLY ONE my.cnf start the instance with the command line option: (E.g. --defaults-file=/home/mysql5123/my.cnf) in this way no side effects will take place (as long you configure correctly my.cnf to work from the new home) let me know if this is enough, enough clear or just was better for me to shut up! Claudio 2009/3/22 s...@twinix.com See Thread at: http://www.techienuggets.com/Detail?tx=78654 Posted on behalf of a User This has proved to be quite challenging. I wasn't able to do the upgrade and basically created another instance of 5.1 and took a backup of my database from 5.0 and restored it to 5.1. Then added all my users, etc. There's got to be a better way? I couldn't figure out how to get the new version 5.1 to see the file system (containing the database) that was in use by 5.0. I looked at all the documents and nowhere (or at least I couldn't see it) does it talk about upgrading the database. When you install the new version how do you get it ot upgrade and use the 5.0 database? Any pointers/help on this would be great for the next time I have to do this. Thanks. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com
Re: upgrading mysql on RHEL4
Hi, Take backup of the existing data before upgrading for safety. There is RHEL 4 specific rpm binary is existing in the downloading section. After installing run the required tools comes with mysql. Before upgrading with existing datas read the documentation carefully. http://dev.mysql.com/doc/refman/5.1/en/installing.html Saravanan --- On Fri, 1/18/08, perl pra [EMAIL PROTECTED] wrote: From: perl pra [EMAIL PROTECTED] Subject: upgrading mysql on RHEL4 To: mysql@lists.mysql.com Date: Friday, January 18, 2008, 10:21 PM Hi Gurus, I have mysql4.x installed on REHL4. Can anybody let me know how to upgrade it to 5.1. Also please tell me where can i get mysql5.1 enterprise edition. Thanks in advance Siva Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: upgrading mysql on RHEL4
Hi ! perl pra schrieb: [[...]] Also please tell me where can i get mysql5.1 enterprise edition. 5.1 is currently labeled rc (current version is 5.1.22-rc), so there is no enterprise edition yet. When there will be one, it will be for paying customers, and they have got (or will receive) the download instructions. HTH, Jörg -- Joerg Bruehe, Senior Production Engineer MySQL AB, www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: upgrading mysql...
On 8/2/06, bruce [EMAIL PROTECTED] wrote: hi.. i have FC3, with 4.1.13, i also have FC4 with 4.1.20. however, i can't seem to find 5.0.x RPMs for FC3/4. do i have to go ahead and build this from source for the FC3/4 boxes that i have... Linux x86 generic RPM at: http://dev.mysql.com/downloads/mysql/5.0.html It wasnt that hard... -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: upgrading mysql on RH fedora core 3
hey... i now have FC2 running mysql-4.1.10a, php5, apache 2.0.51. for some reason, the mysql rpms that i got from rpmfind.net/rpm.pbone, etc... didn't seem to work, as i kept getting weird lib related errors... i started using mysql-3.23 on FC2. i basically followed the path/instructions from http://www.whoopis.com/howtos/php5-mysql4-FC3-rpm.html, replacing my system/requirements where applicable. basic steps: 1) use 'rpm -qa | grep -i mysql' to get all rpms dealing with mysql 2) remove these rpms 'rpm -e ...' 3) get the replacement rpms from www.mysql.com 4) upgrade using 'rpm -Uvh ' 5) resolve any errors/issues... for my system, i only needed to focus on the mysql, as i already had php5 up/running. i chose this approach, as i didn't want to deal with rebuilding from source at this time. good luck!! -Original Message- From: Florin Andrei [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 29, 2005 8:40 PM To: mysql@lists.mysql.com Subject: Re: upgrading mysql on RH fedora core 3 On Tue, 29 Mar 2005 19:28:56 -0800, bruce [EMAIL PROTECTED] wrote: we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running into some serious problems. we had mysql/server (3.23.52-3.i386) running, but needed to go to the higher version... I was about to attempt the same thing. My thinking was to grab the mysql src.rpm from Fedora Core 4 test 1 and rebuild it on FC3: rpmbuild --rebuild mysql...src.rpm Please try that and see how it goes. also, this has to be running with apache/php/perl/etc... My feeling is that apache does not need to be rebuilt. PHP certainly does, from src.rpm, after the new mysql is installed (including mysql-devel). I am not sure whether it would just work to grab the PHP src.rpm from FC3 updates and rebuild it on top of the new mysql, or get the PHP src.rpm from FC4-test and rebuild. Perl is in the same situation, but it's probably even more complex. If i were you, i would probably post on the fedora-test mailing list and ask the same question. Anyway, good luck and let us know how it goes. -- Florin Andrei http://florin.myip.org/ -- 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]
Re: upgrading mysql on RH fedora core 3
On Tue, 29 Mar 2005 19:28:56 -0800, bruce [EMAIL PROTECTED] wrote: we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running into some serious problems. we had mysql/server (3.23.52-3.i386) running, but needed to go to the higher version... I was about to attempt the same thing. My thinking was to grab the mysql src.rpm from Fedora Core 4 test 1 and rebuild it on FC3: rpmbuild --rebuild mysql...src.rpm Please try that and see how it goes. also, this has to be running with apache/php/perl/etc... My feeling is that apache does not need to be rebuilt. PHP certainly does, from src.rpm, after the new mysql is installed (including mysql-devel). I am not sure whether it would just work to grab the PHP src.rpm from FC3 updates and rebuild it on top of the new mysql, or get the PHP src.rpm from FC4-test and rebuild. Perl is in the same situation, but it's probably even more complex. If i were you, i would probably post on the fedora-test mailing list and ask the same question. Anyway, good luck and let us know how it goes. -- Florin Andrei http://florin.myip.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: upgrading mysql on RH fedora core 3
bruce wrote: hi... we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running into some serious problems. we had mysql/server (3.23.52-3.i386) running, but needed to go to the higher version... can someone tell us how/what we need to do to get this working correctly. actually, if anybody's managed to do this, can you tell us exactly what rpm packages you used? as you know, dealing with the rpms gets into dependency hell, which we believe has a lot to do with our issues... if you managed to get this version of mysql running on FC3, and you built it from source, can you provide directions/pointers on what you did, where you placed the resulting libs/etc... also, this has to be running with apache/php/perl/etc... thanks bruce I would strongly suggest backing up your databases first :) I would also ( if possible ) do the import and testing on another PC, while the production server continues. You may have to recompile php and Perl's DBI drivers, or you *may* be able to find some RPMs that will just 'drop in', but I don't use rpms so I couldn't say. The DBI drivers aren't marked as stable yet on my distro ( Gentoo ), so be careful there. If you use ODBC, you will have to upgrade to the latest version of MyODBC - which has some bugs so scan the MyODBC mailing list first. -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: upgrading mysql on RH fedora core 3
On Tuesday, March 29, 2005 21:29, bruce wrote: hi... we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running into some serious problems. we had mysql/server (3.23.52-3.i386) running, but needed to go to the higher version... can someone tell us how/what we need to do to get this working correctly. actually, if anybody's managed to do this, can you tell us exactly what rpm packages you used? as you know, dealing with the rpms gets into dependency hell, which we believe has a lot to do with our issues... if you managed to get this version of mysql running on FC3, and you built it from source, can you provide directions/pointers on what you did, where you placed the resulting libs/etc... also, this has to be running with apache/php/perl/etc... thanks bruce I use mysql primarily on RHEL3, but I just upgraded a FC2 box just to try it. I was able to upgrade it using the rpm's from dev.mysql.com. I did notice one thing. The rpm install didn't seem to kill the old mysqld properly, so I got an access denied right after the install. I ran the following as root: #killall mysqld #service mysql start After that I was then able to connect just fine. As far as perl, php, and apache, everything will continue to work without modification if you continue to use the old password hashes. You can force this. Refer to http://dev.mysql.com/doc/mysql/en/old-client.html, specifically the old-password option. To make perl work with the new passwords, all you need to do is build DBD::mysql from source. To do this, uninstall the dbd-mysql rpm if you have it installed. I can't remember the exact name because I don't use it. Then as root run: #perl -e shell -MCPAN cpaninstall DBD::mysql Regards, -- Tom Crimmins Interface Specialist Pottawattamie County, Iowa -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: upgrading mysql on RH fedora core 3
On Tue, 29 Mar 2005 20:39:54 -0800, Florin Andrei [EMAIL PROTECTED] wrote: On Tue, 29 Mar 2005 19:28:56 -0800, bruce [EMAIL PROTECTED] wrote: we're trying to install mysql/mysql-server (4.1.10a-1.i386) and are running into some serious problems. we had mysql/server (3.23.52-3.i386) running, but needed to go to the higher version... I was about to attempt the same thing. My thinking was to grab the mysql src.rpm from Fedora Core 4 test 1 and rebuild it on FC3: rpmbuild --rebuild mysql...src.rpm Hey, whaddayaknow, it worked! :-) I just rebuilt the FC4t1 mysql src.rpm on FC3. It's just that i cannot try it, not today. I'll see if i can play with it tomorrow. Ideally, i'd like to get a spare system, nuke all it's content, do a fresh minimal install of FC3 (unselect all package categories except development), apply all updates (yum update), rebuild mysql-4, install it, then play with Perl and PHP and see if they need to be rebuilt as well (hopefully not). -- Florin Andrei http://florin.myip.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading mySql from 3.23 to 4.1.10
Hello. Install MySQL-client-4.1.10-0.i386.rpm. Troy Richard [EMAIL PROTECTED] wrote: I have upgraded from mysql 3.23 to 4.1.10 everything seems to be working. I'm trying to run the mysql_fix_privilege_tables script to update the privileges and I'm getting the following error: /usr/bin/mysql_fix_privilege_tables: line 185: /usr/bin/mysql: No such file or directory /usr/bin/mysql existed before I upgraded. I'm not sure what happen to it. I just downloaded the rpms and ran the upgraded. Files downloaded: MySQL-server-4.1.10-0.i386.rpm MySQL-shared-compat-4.1.10-0.i386.rpm Command: rpm -Uvh MySQL* Any help would be a big hand, Thanks Troy -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading MySql on OSX 10.3.6
The directory mysql is a symbolic link to one of the other dirs. If mysql points to old one rename it and make a new one: mv mysql mysqlold ls -s mysql-max-4.1.7-apple-darwin7.5.0-powerpc mysql Do not remove mysql-max-4.0.20-apple-darwin7.3.0-powerpc/data it contains your old databases!!! Santino At 11:17 -0600 10-11-2004, [EMAIL PROTECTED] wrote: I was running ver 4.0.15 and just upgraded to the latest version of 4.1.7. In between I had done an upgrade to ver. 4.0.20. I can get the server to start and stop via the Preferences panel but before and after any upgrade it indicates that 4.0.15 is running. In Navicat which I use as the gui front end it also indicates that 4.0.15 is running. In /usr/local I have 3 MySql related directories: mysql mysql-max-4.1.7-apple-darwin7.5.0-powerpc mysql-max-4.0.20-apple-darwin7.3.0-powerpc My question is how do I get Navicat and the preferences panel to recognize 4.1.7 and do I need to remove 4.0.20 and 4.0.15? Thanks. Kevin -- 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]
RE: Upgrading MySQL erased all data
Thanks. I passed this on and he found what was lost. I guess since the data directory was owned by mysql, he could not find the databases when doing a MacOS file search. I impressed upon him to use a separate datadir as we do with our servers, thus bypassing this whole thing. Thanks again! -steve-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading MySQL erased all data
Are you sure? /usr/local/mysql is a symbolic link to another direcory ( /usr/local/mysql(version). I think the installer overwrite the symbolic link so if you open a terminal and type: ls -l /usr/local Santino At 16:20 -0700 28-10-2004, Steven Roussey wrote: Installing MySQL 4.1.7 (upgrading from 4.1.3) on MacOS X erased the contents of /usr/local/mysql/data -- the privs and data of the previous installation. FYI Luckily (and unfortunately) we have a backup of that database from last week. (The guy that did it here in the office is still in a bit of a frenzy though). -s -- 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]
Re: Upgrading MySQL erased all data
So, do you have a question or are you just bragging? ;-) Rhino - Original Message - From: Steven Roussey [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 28, 2004 7:20 PM Subject: Upgrading MySQL erased all data Installing MySQL 4.1.7 (upgrading from 4.1.3) on MacOS X erased the contents of /usr/local/mysql/data -- the privs and data of the previous installation. FYI Luckily (and unfortunately) we have a backup of that database from last week. (The guy that did it here in the office is still in a bit of a frenzy though). -s -- 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]
Re: Upgrading MySQL. Caveats or Cautions anyone?
Tim Johnson [EMAIL PROTECTED] wrote: The simpliest way: Download and install MySQL Official Binary RPMs from www.mysql.com. They will install on your server and run fine. You'd also want to install the shared-compat RPM in case you have something compiled with older libmysqlclient. The link to read carefully: http://dev.mysql.com/doc/mysql/en/Upgrading-from-3.23.html Hello: Am currently using Ver 11.18 Distrib 3.23.58 on Linux 2.4.20-20.9. (RH 9.0). I'd like to upgrade to the current version. I would like to know if there are any cautions to observe, or any prepartory steps to take. If I look at the following URL: http://dev.mysql.com/downloads/mysql/4.0.html I see some things that confuse me a bit: I see this label: Linux (x86, glibc-2.2, static, gcc) ## Well, I've got glibc-2.3 And I see this label: Linux (x86, glibc-2.3, dynamic, Intel C++ Compiler) ## Well, glibc-2.3 looks good, *but* I don't have ## the Intel C++ Compiler. Just gcc (GCC) 3.2.2 Comments and pointers to docs would be appreciated. Thanks much tim -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Upgrading MySQL. Caveats or Cautions anyone?
Hi, I found that the Intel C++ version needed some libraries which weren't on my RH9.0 system (this was when upgrading to 4.1.4g): libcprts.so.5 libcxa.so.5 libunwind.so.5 This seems to have been reported many times e.g. http://bugs.mysql.com/bug.php?id=4408 The resolve was to get the libs from: ftp://ftp.mysql.com/pub/mysql/download/icc-8.0-libs.tar.gz MD5 checksum: 0970bbfb9fb076dfe995b3176bf90fad Then extract them and put them somewhere sensible (I chose /usr/local/lib) and then run ldconfig to find them. Without these libs none of the mysql apps would start. I guess 4.1.5g may have packaged the libs with the tarball, I don't know. Thanks, Mike -Original Message- From: Tim Johnson [mailto:[EMAIL PROTECTED] Sent: 18 September 2004 03:43 To: [EMAIL PROTECTED] Subject: Upgrading MySQL. Caveats or Cautions anyone? Hello: Am currently using Ver 11.18 Distrib 3.23.58 on Linux 2.4.20-20.9. (RH 9.0). I'd like to upgrade to the current version. I would like to know if there are any cautions to observe, or any prepartory steps to take. If I look at the following URL: http://dev.mysql.com/downloads/mysql/4.0.html I see some things that confuse me a bit: I see this label: Linux (x86, glibc-2.2, static, gcc) ## Well, I've got glibc-2.3 And I see this label: Linux (x86, glibc-2.3, dynamic, Intel C++ Compiler) ## Well, glibc-2.3 looks good, *but* I don't have ## the Intel C++ Compiler. Just gcc (GCC) 3.2.2 Comments and pointers to docs would be appreciated. Thanks much tim -- Tim Johnson [EMAIL PROTECTED] http://www.alaska-internet-solutions.com -- 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]
Re: Upgrading MySQL. Caveats or Cautions anyone?
You can ignore both of those if you use the binaries. -Eric On Fri, 17 Sep 2004 18:43:02 -0800, Tim Johnson [EMAIL PROTECTED] wrote: Hello: Am currently using Ver 11.18 Distrib 3.23.58 on Linux 2.4.20-20.9. (RH 9.0). I'd like to upgrade to the current version. I would like to know if there are any cautions to observe, or any prepartory steps to take. If I look at the following URL: http://dev.mysql.com/downloads/mysql/4.0.html I see some things that confuse me a bit: I see this label: Linux (x86, glibc-2.2, static, gcc) ## Well, I've got glibc-2.3 And I see this label: Linux (x86, glibc-2.3, dynamic, Intel C++ Compiler) ## Well, glibc-2.3 looks good, *but* I don't have ## the Intel C++ Compiler. Just gcc (GCC) 3.2.2 Comments and pointers to docs would be appreciated. Thanks much tim -- Tim Johnson [EMAIL PROTECTED] http://www.alaska-internet-solutions.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- Eric Bergen [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading Mysql and Perl DBD
This is covered in the manual http://dev.mysql.com/doc/mysql/en/Password_hashing.html: A 4.1 client can connect to a pre-4.1 server, because the client understands both the old and new password hashing mechanisms. So, if you build the Perl modules against the 4.1.x library, you should be able to connect to either server. Michael sean c peters wrote: I now have MySQL 4.0.2 and MySQL 4.1.3 beta both installed and running on one machine. I want to be able to use the Perl DBI / DBD to connect to both servers. I understand that there have been some changes between the MySQL 4.0.X and 4.1.X series that may require differently compiled DBD's. So my question is, do i need to have 2 separate DBD versions, or will the newer one work for both MySQL servers. The old DBD does not work for the new server. This is demonstrated by the error message: DBI-connect(...) failed: Client does not support authentication protocol requested by server; consider upgrading MySQL client at connect_test.pl line 19 All the connect_test.pl tries to do is create a db connection to each server separately. Any insight would be greatly appreciated thanks much sean peters [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading mySQL 3.23 to 4.0
Can you give me a bit more detailed instructions on what i am uninstalling and what I should back up? Thanks Wolfgang Riedel wrote: [EMAIL PROTECTED] schrieb: I am trying to upgrade to the new version of mySQL on Fedora Core 2 Linux. I have mysql Ver 11.18 Distrib 3.23.58, for redhat-linux-gnu (i386) some days ago, I had the same problem. Redhat's rpm packages mysql-3* and MySQL's new packages MySQL-4.0.20* are not compatible, because the are build in different ways - different nameing scheme and different content. Thatswhy this is no good idea to try rpm -Uvh I've deinstalled the old packages by rpm -e ... (save /etc/my.cnf and /var/lib/mysql before) and installed the new one on a 'mysql-clean' base. Bye, Wolfgang -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading mySQL 3.23 to 4.0
At 01:58 PM 8/2/2004, [EMAIL PROTECTED] wrote: Greetings: I am trying to upgrade to the new version of mySQL on Fedora Core 2 Linux. I have mysql Ver 11.18 Distrib 3.23.58, for redhat-linux-gnu (i386) I downloaded the following files: MySQL-client-4.0.20-0.i386.rpm MySQL-server-4.0.20-0.i386.rpm and as root ran the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm MySQL-client-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 error: Failed dependencies: libmysqlclient.so.10 is needed by (installed) perl-DBD-MySQL-2.9003-4 libmysqlclient.so.10 is needed by (installed) mod_auth_mysql-20030510-4.1 libmysqlclient.so.10 is needed by (installed) php-mysql-4.3.4-11 [EMAIL PROTECTED] Desktop]# I am not sure what I need to do can someone please assist. Thank You Gary Install - MySQL-shared-4.0.20-0.i386.rpm, and - MySQL-shared-compat-4.0.20-0.i386.rpm as well. And probably MySQL-devel-4.0.20-0.i386.rpm just for kicks. The 2nd one is the specific package that should solve the problem, especially with the php-mysql package. HTH, Japheth J.C. Cleaver -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading mySQL 3.23 to 4.0
I wound up having to do the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-compat-4.0.20-0.i386.rpm warning: MySQL-shared-compat-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing...### [100%] 1:MySQL-shared-compat### [100%] [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-4.0.20-0.i386.rpm warning: MySQL-shared-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing...### [100%] package MySQL-shared-4.0.20-0 is already installed [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-devel-4.0.20-0.i386.rpm warning: MySQL-devel-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing...### [100%] file /usr/bin/comp_err from install of MySQL-devel-4.0.20-0 conflicts with file from package mysql-3.23.58-9 file /usr/bin/mysql_config from install of MySQL-devel-4.0.20-0 conflicts with file from package mysql-3.23.58-9 [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm MySQL-client-4.0.20-0.i386.rpm MySQL-devel-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing...### [100%] 1:MySQL-server ### [ 33%] Installing all prepared tables 040802 17:21:17 Warning: Asked for 196608 thread stack, but got 126976 040802 17:21:17 /usr/sbin/mysqld: Shutdown Complete PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h localhost.localdomain password 'new-password' See the manual for more instructions. NOTE: If you are upgrading from a MySQL = 3.22.10 you should run the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be able to use the new GRANT command! Please report any problems with the /usr/bin/mysqlbug script! The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at https://order.mysql.com 2:MySQL-client ### [ 67%] 3:MySQL-devel### [100%] [EMAIL PROTECTED] Desktop]# Does this mean success? Also, what does this line mean? 040802 17:21:17 Warning: Asked for 196608 thread stack, but got 126976 Thanks for the help - Original Message - From: Japheth Cleaver [EMAIL PROTECTED] Date: Monday, August 2, 2004 5:12 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 At 01:58 PM 8/2/2004, [EMAIL PROTECTED] wrote: Greetings: I am trying to upgrade to the new version of mySQL on Fedora Core 2 Linux. I have mysql Ver 11.18 Distrib 3.23.58, for redhat- linux-gnu (i386) I downloaded the following files: MySQL-client-4.0.20-0.i386.rpm MySQL-server-4.0.20-0.i386.rpm and as root ran the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm MySQL-client-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 error: Failed dependencies: libmysqlclient.so.10 is needed by (installed) perl-DBD- MySQL-2.9003-4 libmysqlclient.so.10 is needed by (installed) mod_auth_mysql-20030510-4.1 libmysqlclient.so.10 is needed by (installed) php-mysql- 4.3.4-11 [EMAIL PROTECTED] Desktop]# I am not sure what I need to do can someone please assist. Thank You Gary Install - MySQL-shared-4.0.20-0.i386.rpm, and - MySQL-shared-compat-4.0.20-0.i386.rpm as well. And probably MySQL-devel-4.0.20-0.i386.rpm
Re: Upgrading mySQL 3.23 to 4.0
I am now getting [EMAIL PROTECTED] Desktop]# mysql -u root -pmypasshere ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) any thoughts... once again thanks for the assistance - Original Message - From: [EMAIL PROTECTED] Date: Monday, August 2, 2004 5:26 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 I wound up having to do the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-compat-4.0.20- 0.i386.rpm warning: MySQL-shared-compat-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] 1:MySQL-shared-compat ### [100%] [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-4.0.20-0.i386.rpm warning: MySQL-shared-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] package MySQL-shared-4.0.20-0 is already installed [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-devel-4.0.20-0.i386.rpm warning: MySQL-devel-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] file /usr/bin/comp_err from install of MySQL-devel-4.0.20-0 conflicts with file from package mysql-3.23.58-9 file /usr/bin/mysql_config from install of MySQL-devel- 4.0.20-0 conflicts with file from package mysql-3.23.58-9 [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm MySQL-client-4.0.20-0.i386.rpm MySQL-devel-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] 1:MySQL-server ### [ 33%] Installing all prepared tables 040802 17:21:17 Warning: Asked for 196608 thread stack, but got 126976040802 17:21:17 /usr/sbin/mysqld: Shutdown Complete PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h localhost.localdomain password 'new- password'See the manual for more instructions. NOTE: If you are upgrading from a MySQL = 3.22.10 you should run the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be able to use the new GRANT command! Please report any problems with the /usr/bin/mysqlbug script! The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at https://order.mysql.com 2:MySQL-client ### [ 67%] 3:MySQL-devel ### [100%] [EMAIL PROTECTED] Desktop]# Does this mean success? Also, what does this line mean? 040802 17:21:17 Warning: Asked for 196608 thread stack, but got 126976 Thanks for the help - Original Message - From: Japheth Cleaver [EMAIL PROTECTED] Date: Monday, August 2, 2004 5:12 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 At 01:58 PM 8/2/2004, [EMAIL PROTECTED] wrote: Greetings: I am trying to upgrade to the new version of mySQL on Fedora Core 2 Linux. I have mysql Ver 11.18 Distrib 3.23.58, for redhat- linux-gnu (i386) I downloaded the following files: MySQL-client-4.0.20-0.i386.rpm MySQL-server-4.0.20-0.i386.rpm and as root ran the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20- 0.i386.rpm MySQL-client-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 error: Failed dependencies: libmysqlclient.so.10 is needed
Re: Upgrading mySQL 3.23 to 4.0
in my Linux Services... the mysqld entry is missing i have mysql and that is supposedly running. - Original Message - From: Carlos Proal [EMAIL PROTECTED] Date: Monday, August 2, 2004 6:19 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 The upgrade shutdown the database, i think you must restart it manually, maybe using some of the init scripts. Carlos From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Japheth Cleaver [EMAIL PROTECTED] Subject: Re: Upgrading mySQL 3.23 to 4.0 Date: Mon, 02 Aug 2004 17:31:03 -0400 I am now getting [EMAIL PROTECTED] Desktop]# mysql -u root -pmypasshere ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) any thoughts... once again thanks for the assistance - Original Message - From: [EMAIL PROTECTED] Date: Monday, August 2, 2004 5:26 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 I wound up having to do the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-compat-4.0.20- 0.i386.rpm warning: MySQL-shared-compat-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] 1:MySQL-shared-compat ### [100%] [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-4.0.20-0.i386.rpm warning: MySQL-shared-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] package MySQL-shared-4.0.20-0 is already installed [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-devel-4.0.20-0.i386.rpm warning: MySQL-devel-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] file /usr/bin/comp_err from install of MySQL-devel- 4.0.20-0 conflicts with file from package mysql-3.23.58-9 file /usr/bin/mysql_config from install of MySQL-devel- 4.0.20-0 conflicts with file from package mysql-3.23.58-9 [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm MySQL-client-4.0.20-0.i386.rpm MySQL-devel-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] 1:MySQL-server ### [ 33%] Installing all prepared tables 040802 17:21:17 Warning: Asked for 196608 thread stack, but got 126976040802 17:21:17 /usr/sbin/mysqld: Shutdown Complete PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h localhost.localdomain password 'new- password'See the manual for more instructions. NOTE: If you are upgrading from a MySQL = 3.22.10 you should run the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be able to use the new GRANT command! Please report any problems with the /usr/bin/mysqlbug script! The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at https://order.mysql.com 2:MySQL-client ### [ 67%] 3:MySQL-devel ### [100%] [EMAIL PROTECTED] Desktop]# Does this mean success? Also, what does this line mean? 040802 17:21:17 Warning: Asked for 196608 thread stack, but got 126976 Thanks for the help - Original Message - From: Japheth Cleaver [EMAIL PROTECTED] Date: Monday, August 2, 2004 5:12 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 At 01:58 PM 8/2/2004, [EMAIL PROTECTED] wrote: Greetings: I am trying to upgrade to the new version of mySQL on Fedora Core 2 Linux. I have mysql Ver 11.18 Distrib 3.23.58, for redhat- linux-gnu (i386) I downloaded the following files: MySQL-client-4.0.20-0.i386.rpm MySQL-server-4.0.20-0.i386.rpm and as root ran the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20- 0.i386.rpm MySQL-client-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 error: Failed dependencies: libmysqlclient.so.10 is needed by (installed) perl- DBD- MySQL-2.9003-4 libmysqlclient.so.10 is needed by (installed) mod_auth_mysql-20030510-4.1 libmysqlclient.so.10 is needed by (installed) php- mysql- 4.3.4-11 [EMAIL PROTECTED] Desktop]# I am not sure what I need to do can someone please assist. Thank You Gary Install - MySQL-shared-4.0.20-0.i386.rpm
Re: Upgrading mySQL 3.23 to 4.0
supposedly ?, you can check if the mysqld daemon is running with: ps -ef | grep mysql if the daemon is running then the error is something else but my first bet is that is not running. Carlos From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Carlos Proal [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Upgrading mySQL 3.23 to 4.0 Date: Mon, 02 Aug 2004 18:26:05 -0400 in my Linux Services... the mysqld entry is missing i have mysql and that is supposedly running. - Original Message - From: Carlos Proal [EMAIL PROTECTED] Date: Monday, August 2, 2004 6:19 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 The upgrade shutdown the database, i think you must restart it manually, maybe using some of the init scripts. Carlos From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: Japheth Cleaver [EMAIL PROTECTED] Subject: Re: Upgrading mySQL 3.23 to 4.0 Date: Mon, 02 Aug 2004 17:31:03 -0400 I am now getting [EMAIL PROTECTED] Desktop]# mysql -u root -pmypasshere ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) any thoughts... once again thanks for the assistance - Original Message - From: [EMAIL PROTECTED] Date: Monday, August 2, 2004 5:26 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 I wound up having to do the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-compat-4.0.20- 0.i386.rpm warning: MySQL-shared-compat-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] 1:MySQL-shared-compat ### [100%] [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-shared-4.0.20-0.i386.rpm warning: MySQL-shared-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] package MySQL-shared-4.0.20-0 is already installed [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-devel-4.0.20-0.i386.rpm warning: MySQL-devel-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] file /usr/bin/comp_err from install of MySQL-devel- 4.0.20-0 conflicts with file from package mysql-3.23.58-9 file /usr/bin/mysql_config from install of MySQL-devel- 4.0.20-0 conflicts with file from package mysql-3.23.58-9 [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20-0.i386.rpm MySQL-client-4.0.20-0.i386.rpm MySQL-devel-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Preparing... ### [100%] 1:MySQL-server ### [ 33%] Installing all prepared tables 040802 17:21:17 Warning: Asked for 196608 thread stack, but got 126976040802 17:21:17 /usr/sbin/mysqld: Shutdown Complete PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h localhost.localdomain password 'new- password'See the manual for more instructions. NOTE: If you are upgrading from a MySQL = 3.22.10 you should run the /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be able to use the new GRANT command! Please report any problems with the /usr/bin/mysqlbug script! The latest information about MySQL is available on the web at http://www.mysql.com Support MySQL by buying support/licenses at https://order.mysql.com 2:MySQL-client ### [ 67%] 3:MySQL-devel ### [100%] [EMAIL PROTECTED] Desktop]# Does this mean success? Also, what does this line mean? 040802 17:21:17 Warning: Asked for 196608 thread stack, but got 126976 Thanks for the help - Original Message - From: Japheth Cleaver [EMAIL PROTECTED] Date: Monday, August 2, 2004 5:12 pm Subject: Re: Upgrading mySQL 3.23 to 4.0 At 01:58 PM 8/2/2004, [EMAIL PROTECTED] wrote: Greetings: I am trying to upgrade to the new version of mySQL on Fedora Core 2 Linux. I have mysql Ver 11.18 Distrib 3.23.58, for redhat- linux-gnu (i386) I downloaded the following files: MySQL-client-4.0.20-0.i386.rpm MySQL-server-4.0.20-0.i386.rpm and as root ran the following: [EMAIL PROTECTED] Desktop]# rpm -Uvh MySQL-server-4.0.20- 0.i386.rpm MySQL-client-4.0.20-0.i386.rpm warning: MySQL-server-4.0.20-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 error: Failed dependencies: libmysqlclient.so.10 is needed by (installed) perl
Re: Upgrading mySQL 3.23 to 4.0
On Mon, 02 Aug 2004 17:31:03 -0400 [EMAIL PROTECTED] wrote: I am now getting [EMAIL PROTECTED] Desktop]# mysql -u root -pmypasshere ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) any thoughts... once again thanks for the assistance It seems like your MySQL server is not running. Try: # /etc/init.d/mysql start And check what does the error log say. On my Fedora it is in: /var/lib/mysql/hostname.err -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading MySQL on RedHat 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wed, 2 Jul 2003, Paul DuBois wrote: At 11:33 -0400 7/2/03, Andrew Pierce wrote: I am getting ready to try to upgrade MySQL on my RedHat 9 box. I want to go from the version that came with the distro (version 3.23.54) to the latest (verion 4.0). Just thought I'd post to get a heads-up on any known issues or prerequisites. I just hate it when I try something like this and screw up my whole installation. My planned steps are to: 1. mysqldump everything to a backup file 2. stop the service 3. uninstall all the current rpm's 4. install the fresh rpm's 5. startup 6. \. the file from step 1 Anything I need to lookout for? If you want to keep apps that shipped with the distro but are linked against the 3.23 libmysqlclient, you may want to install MySQL-shared-compat to satisfy the RPM library dependencies. That should work, but after you install the new RPM files, use chkconfig --list mysql to make sure that the server is set to start on runlevels 2 through 5. If it's not, use: chkconfig --levels 2345 mysql on Otherwise, the server won't start automatically at system boot time. This problem has been seen on RH 8 and RH 9. I understand it's been fixed now, but I'm not sure if the fix is in the current release or the next one. It will be fixed for 4.0.14: http://bugs.mysql.com/bug.php?id=272 Bye, LenZ - -- Lenz Grimmer [EMAIL PROTECTED] Senior Production Engineer MySQL GmbH, http://www.mysql.de/ Hamburg, Germany For technical support contracts, visit https://order.mysql.com/?ref=mlgr -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE/BIQsSVDhKrJykfIRAsaIAJ0RkCCcoWOTJ1gHCkZ+MSvvt3vxBACfeW7X P7xkEZ1GfESz7bwMpF4+5/E= =aHHD -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Upgrading MySQL on RedHat 9
At 11:33 -0400 7/2/03, Andrew Pierce wrote: I am getting ready to try to upgrade MySQL on my RedHat 9 box. I want to go from the version that came with the distro (version 3.23.54) to the latest (verion 4.0). Just thought I'd post to get a heads-up on any known issues or prerequisites. I just hate it when I try something like this and screw up my whole installation. My planned steps are to: 1. mysqldump everything to a backup file 2. stop the service 3. uninstall all the current rpm's 4. install the fresh rpm's 5. startup 6. \. the file from step 1 Anything I need to lookout for? That should work, but after you install the new RPM files, use chkconfig --list mysql to make sure that the server is set to start on runlevels 2 through 5. If it's not, use: chkconfig --levels 2345 mysql on Otherwise, the server won't start automatically at system boot time. This problem has been seen on RH 8 and RH 9. I understand it's been fixed now, but I'm not sure if the fix is in the current release or the next one. Thanks. Andrew -- Paul DuBois, Senior Technical Writer Madison, Wisconsin, USA MySQL AB, www.mysql.com Are you MySQL certified? http://www.mysql.com/certification/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: upgrading mysql
[EMAIL PROTECTED] wrote: Can someone help point me in the right direction? Thanks I just finished a practice upgrade (on a back-up server) myself and will be upgrading the real server during off-peak hours soon. We are running win2k servers so I can't speak directly to any linux issues, but generically speaking, upgrading to 3.23.56 was easy: I downloaded the installation files to my server and unzipped them. Stopped the MySQL service AND mysqladmin (you will have errors if you don't do this!). Then ran the setup.exe, restarted the service, checked mysql admin and saw that the version had been updated, and smiled. I would imagine if you follow the corresponding linux-steps, you should have no problems. Good luck, Tab mysql - 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: upgrading mysql
On a linux box you do not have to stop everything like on Windows. We always leave our current version running, install the upgrade in a new location with a new data dir (a snapshot of the live one). We run the new install on a different port than the live install so we can test it and what not before switching over. We always leave our installs in a directory that gives the version info like mysql-3.23.55-pc-linux-i686 and then symlink a directory named mysql to the version that should be live. So when we decide it is time to go live with the new install we change the conf to point to the correct data dir and to be on the right port, stop mysqld, change the symlink and then restart with the new version. This allows for easy rollbacks just in case. We have had really poor luck with building from source on our VA Linux box and have used the binaries for the last two or three upgrades. Our builds were really unstable and buggy under a high load, but the binaries have been great. Hope that helps -Original Message- From: Tab Alleman [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 2:14 PM To: [EMAIL PROTECTED] Subject: RE: upgrading mysql [EMAIL PROTECTED] wrote: Can someone help point me in the right direction? Thanks I just finished a practice upgrade (on a back-up server) myself and will be upgrading the real server during off-peak hours soon. We are running win2k servers so I can't speak directly to any linux issues, but generically speaking, upgrading to 3.23.56 was easy: I downloaded the installation files to my server and unzipped them. Stopped the MySQL service AND mysqladmin (you will have errors if you don't do this!). Then ran the setup.exe, restarted the service, checked mysql admin and saw that the version had been updated, and smiled. I would imagine if you follow the corresponding linux-steps, you should have no problems. Good luck, Tab mysql - 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: upgrading mysql
Thank you for your reply. OK, I understand that. So what are the steps to install the file. Isn't there an RPM or something. Do I take the 4.0 binary and place it an any folder on my box? Then go to that directory and type a lynix command to unpack and install the files? Then, go to the config file (not sure which one), maybe the one in my database and point it to the new mqsql program? I relly appreciate your help. Thanks, Mike The following message was sent by Jennifer Goodie [EMAIL PROTECTED] on Fri, 21 Mar 2003 14:36:43 -0800. On a linux box you do not have to stop everything like on Windows. We always leave our current version running, install the upgrade in a new location with a new data dir (a snapshot of the live one). We run the new install on a different port than the live install so we can test it and what not before switching over. We always leave our installs in a directory that gives the version info like mysql-3.23.55-pc-linux-i686 and then symlink a directory named mysql to the version that should be live. So when we decide it is time to go live with the new install we change the conf to point to the correct data dir and to be on the right port, stop mysqld, change the symlink and then restart with the new version. This allows for easy rollbacks just in case. We have had really poor luck with building from source on our VA Linux box and have used the binaries for the last two or three upgrades. Our builds were really unstable and buggy under a high load, but the binaries have been great. Hope that helps -Original Message- From: Tab Alleman [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 2:14 PM To: [EMAIL PROTECTED] Subject: RE: upgrading mysql [EMAIL PROTECTED] wrote: Can someone help point me in the right direction? Thanks I just finished a practice upgrade (on a back-up server) myself and will be upgrading the real server during off-peak hours soon. We are running win2k servers so I can't speak directly to any linux issues, but generically speaking, upgrading to 3.23.56 was easy: I downloaded the installation files to my server and unzipped them. Stopped the MySQL service AND mysqladmin (you will have errors if you don't do this!). Then ran the setup.exe, restarted the service, checked mysql admin and saw that the version had been updated, and smiled. I would imagine if you follow the corresponding linux-steps, you should have no problems. Good luck, Tab mysql - 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: upgrading mysql
These links may help: 2.5.2 Upgrading From Version 3.23 to Version 4.0 http://www.mysql.com/doc/en/Upgrading-from-3.23.html 2.1.1 Installing MySQL on Linux http://www.mysql.com/doc/en/Linux-RPM.html 2.6.1.1 Linux Notes for Binary Distributions http://www.mysql.com/doc/en/Binary_notes-Linux.html 2.2 General Installation Issues http://www.mysql.com/doc/en/General_Installation_Issues.html At 16:59 -0500 3/21/03, [EMAIL PROTECTED] wrote: Thank you for your reply. OK, I understand that. So what are the steps to install the file. Isn't there an RPM or something. Do I take the 4.0 binary and place it an any folder on my box? Then go to that directory and type a lynix command to unpack and install the files? Then, go to the config file (not sure which one), maybe the one in my database and point it to the new mqsql program? I relly appreciate your help. Thanks, Mike The following message was sent by Jennifer Goodie [EMAIL PROTECTED] on Fri, 21 Mar 2003 14:36:43 -0800. On a linux box you do not have to stop everything like on Windows. We always leave our current version running, install the upgrade in a new location with a new data dir (a snapshot of the live one). We run the new install on a different port than the live install so we can test it and what not before switching over. We always leave our installs in a directory that gives the version info like mysql-3.23.55-pc-linux-i686 and then symlink a directory named mysql to the version that should be live. So when we decide it is time to go live with the new install we change the conf to point to the correct data dir and to be on the right port, stop mysqld, change the symlink and then restart with the new version. This allows for easy rollbacks just in case. We have had really poor luck with building from source on our VA Linux box and have used the binaries for the last two or three upgrades. Our builds were really unstable and buggy under a high load, but the binaries have been great. Hope that helps -Original Message- From: Tab Alleman [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 2:14 PM To: [EMAIL PROTECTED] Subject: RE: upgrading mysql [EMAIL PROTECTED] wrote: Can someone help point me in the right direction? Thanks I just finished a practice upgrade (on a back-up server) myself and will be upgrading the real server during off-peak hours soon. We are running win2k servers so I can't speak directly to any linux issues, but generically speaking, upgrading to 3.23.56 was easy: I downloaded the installation files to my server and unzipped them. Stopped the MySQL service AND mysqladmin (you will have errors if you don't do this!). Then ran the setup.exe, restarted the service, checked mysql admin and saw that the version had been updated, and smiled. I would imagine if you follow the corresponding linux-steps, you should have no problems. Good luck, Tab mysql - 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 -- Jeff Shapiro, Colorado Springs, CO, USA At work I *have* to use a Windows machine, at home I *get* to use a Mac. - 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: Upgrading MySQL/Solaris 2.7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 17 Dec 2002, John P wrote: I want to upgrade my MySQL version (3.23.51) because of the recently revealed exploit; the only binary dist on mysql.com for solaris 2.7 is 3.23.53; will there be a problem compiling from source on this platform or should I wait for the binaries to be updated? There is a .54 release for 2.8 and 2.9 but not for 2.7. Or does this exploit not affect Solaris? Unfortunately it does affect all platforms. Sadly, our Solaris 2.7 build host has died (hardware failure) and we are currently unable to provide a 3.23.54 binary for Solaris 2.7 - sorry about that. However, I've already received a hint from a user who is using our Solaris 2.8 binary on a 2.7 system - you might want to try that first before doing a compile by yourself. Bye, LenZ - -- For technical support contracts, visit https://order.mysql.com/?ref=mlgr __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Mr. Lenz Grimmer [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Production Engineer /_/ /_/\_, /___/\___\_\___/ Hamburg, Germany ___/ www.mysql.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9/4ijSVDhKrJykfIRAsOqAJ46tYXvOiNnT7I8wqiVEYToO9WrTQCeNzPs AQzcmaregampBpI8ff/B+Rs= =FVJq -END PGP SIGNATURE- - 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: Upgrading MySQL from 3.23.41 to 3.23.53a
You might need to use rpm -e to uninstall previous version first. Check the documentation. ~Kelly W. Black -Original Message- From: Rick Root [mailto:rroot;wakeinternet.com] Sent: Wednesday, November 13, 2002 10:47 AM To: mysql Subject: Upgrading MySQL from 3.23.41 to 3.23.53a I would like to upgrade MySQL to the latest production release (3.23.53a) from my current 3.23.41 I have the following packages installed already: mysql-devel-3.23.41-1 mysqlclient9-3.23.22-6 mysql-3.23.41-1 mysql-server-3.23.41-1 What do I need to do in order to upgrade to the newest version? I tried using the RPM facility to install and upgrade the new packages I just downloaded but I get conflicts... ie... [root@frodo MySQL]# rpm --install MySQL-3.23.53a-1.i386.rpm error: failed dependencies: MySQL conflicts with mysql-3.23.41-1 MySQL-server conflicts with mysql-server-3.23.41-1 [root@frodo MySQL]# rpm -U MySQL-3.23.53a-1.i386.rpm error: failed dependencies: MySQL-server conflicts with mysql-server-3.23.41-1 libmysqlclient.so.10 is needed by mysql-server-3.23.41-1 libmysqlclient.so.10 is needed by perl-DBD-MySQL-1.2216-4 [root@frodo MySQL]# So what should I do? Do I need to actually remove the old MySQL first and then install the new one? - Rick Root - 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 - 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: Upgrading MySQL from 3.23.41 to 3.23.53a
At 13:47 2002-11-13 -0500, Rick Root wrote: [root@frodo MySQL]# rpm --install MySQL-3.23.53a-1.i386.rpm error: failed dependencies: MySQL conflicts with mysql-3.23.41-1 MySQL-server conflicts with mysql-server-3.23.41-1 [root@frodo MySQL]# rpm -U MySQL-3.23.53a-1.i386.rpm error: failed dependencies: MySQL-server conflicts with mysql-server-3.23.41-1 libmysqlclient.so.10 is needed by mysql-server-3.23.41-1 So what should I do? Do I need to actually remove the old MySQL first and then install the new one? You are trying to replace the redhat installed mysql with MySQL:s rpms. Do things in this order and it should work (I don't promise it will work =) 1. do a full mysqldump of all your databases. 2. shutdown and remove mysql with rpm -e your-old-package 3. Install the new mysql, start it and check if your databases are intact. Else restore from dumps. regards /Lars - 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: Upgrading mysql from 3.22 to 3.23
Hi, On Tue, 2002-03-19 at 11:41, Campbell McLeay wrote: I wish to upgrade mysql server from 3.22 to 3.23 running on Linux and had a few basic questions which I am hoping someone can help me with. My plan is simply to download and unpack the binary distribution, stop mysqld, move the symlink to point to the new distribution, and restart. However, I was wondering what data files had to be moved across and how this might be done. At a guess, I would assume everything in the 'data' subdirectory of the old distro should be copied across (using e.g., 'cp -pR') but I also noticed that there a number of files in the root directory called 'recoftrans.XXX', where 'XXX' is a 3 digit number. Do these have to be moved as well? And is there anything else that has to be copied? Any help greatly appreciated. http://www.mysql.com/doc/U/p/Upgrading-from-3.22.html Regards, Arjen. -- Get MySQL Training Worldwide, http://www.mysql.com/training/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Arjen G. Lentz [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Technical Writer, Trainer /_/ /_/\_, /___/\___\_\___/ Brisbane, QLD Australia ___/ www.mysql.com - 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: upgrading mysql-3.23.48 and rpm package.
hi, on redhat 6.2, you have a package manager (rpm) version which cannot interpret rpm's created with package manager version 4. afaik, rpm 3.0.6 is able to read both formats, so you should upgrade your package manager software to version 3.0.6 to be able to install the new mysql package. don't know if there any libc issues, though. bye michael Ireneusz Piasecki wrote: Hi all. I would upgrade my mysql serever from RPM: rpm -i MySQL-3.23.48-1.i386.rpm only packages with major numbers = 3 are supported by this version of RPM error: MySQL-3.23.48-1.i386.rpm cannot be installed What can i solve this problem. I use Red Hat 6.2 Where can i find the RPM engine to install mysql 3.23.48 ? With mysql 3.23.47 was no problem Pleas help. Regards I. Piasecki -- Okresl Swoje potrzeby - my znajdziemy oferte za Ciebie! [ http://oferty.onet.pl ] - 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 - 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: upgrading mysql-3.23.48 and rpm package.
Ireneusz, Tuesday, February 12, 2002, 11:46:40 AM, you wrote: IP HI. IP No i get twice the .rpm of mysql-3.23.48. It is'nt corrupted. IP I could'nt install it. IP I have rpm 3.0.4. on my RH 6.2 (Zoot) box. IP Is there on the NET, rpm package of mysql-3.23.48, which can i install with IP rpm 3.0.4 ? Try to install with a commandline like this: rpm -i -v MySQL-3.23.48-1.i386.rpm Adding -v will probably show you the cause of your trouble. IP Hi all. IP I would upgrade my mysql serever from RPM: IP rpm -i MySQL-3.23.48-1.i386.rpm IP only packages with major numbers = 3 are supported by this version of IP RPM IP error: MySQL-3.23.48-1.i386.rpm cannot be installed IP What can i solve this problem. I use Red Hat 6.2 IP Where can i find the RPM engine to install mysql 3.23.48 ? IP With mysql 3.23.47 was no problem May be you have a corrupted installation package. Try to download the MySQL 3.23.48 (rpm) again from: http://www.mysql.com/downloads/mysql-3.23.html IP Pleas help. IP Regards IP I. Piasecki -- For technical support contracts, goto https://order.mysql.com/ This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - 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: upgrading mysql-3.23.48 and rpm package.
HI. No i get twice the .rpm of mysql-3.23.48. It is'nt corrupted. I could'nt install it. I have rpm 3.0.4. on my RH 6.2 (Zoot) box. Is there on the NET, rpm package of mysql-3.23.48, which can i install with rpm 3.0.4 ? - Original Message - From: Egor Egorov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 11, 2002 4:46 PM Subject: upgrading mysql-3.23.48 and rpm package. Ireneusz, Monday, February 11, 2002, 5:16:53 PM, you wrote: IP Hi all. IP I would upgrade my mysql serever from RPM: IP rpm -i MySQL-3.23.48-1.i386.rpm IP only packages with major numbers = 3 are supported by this version of RPM IP error: MySQL-3.23.48-1.i386.rpm cannot be installed IP What can i solve this problem. I use Red Hat 6.2 IP Where can i find the RPM engine to install mysql 3.23.48 ? IP With mysql 3.23.47 was no problem May be you have a corrupted installation package. Try to download the MySQL 3.23.48 (rpm) again from: http://www.mysql.com/downloads/mysql-3.23.html IP Pleas help. IP Regards IP I. Piasecki -- For technical support contracts, goto https://order.mysql.com/ This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - 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 -- Tego nie znajdziesz w zadnym sklepie! [ http://oferty.onet.pl ] - 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: Upgrading mysql on Win2K
Date |Tue, 7 Aug 2001 13:07:46 -0700 From |A. Clausen [EMAIL PROTECTED] Hello! AC What is the process of upgrading v3.23.36 to 3.23.40 on Windows NT. Can I just install over top or is there some other steps that should be taken? No.You can just install new version. AC I am running two mysql servers, one a master and one a slave. Does this make a difference? No. ___ For technical support contracts, visit https://order.mysql.com/ This email is sponsored by SWSoft, http://www.asplinux.ru/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Grigory Bakunov [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB / SWSoft /_/ /_/\_, /___/\___\_\___/ ___/ www.mysql.com - 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: Upgrading MySQL on Windows Platform
Yes, just stop the mysql service before you begin installation by running something like net stop mysql from a command prompt. Hi everyone, I'm kinda new with MySQL and I have a question about upgrading MySQL to a newer version on Windows 2000 OS. Is there any special command that I should run or should I just re-install the latest version 3.23.39. Will it overwrite the old version automatically while preserving all the tables and databases? Please help. Thanks. - 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: Upgrading MySQL on Windows Platform
At 14:32 21/06/2001 -0700, Martin Tunggorono wrote: Hi! Hi everyone, I'm kinda new with MySQL and I have a question about upgrading MySQL to a newer version on Windows 2000 OS. Is there any special command that I should run or should I just re-install the latest version 3.23.39. Will it overwrite the old version automatically while preserving all the tables and databases? Please help. Thanks. The databases aren't overwrite. However before to run the setup, in the today distribution delete the older share directory for the err files to be updated. This distribution should be changed by one identify by the mysql-3.23.39a-win.zip. However, is always a good safe to make the backup of the databases, to avoid problem outside of the setup program. Regards, Miguel Martin - 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 -- For technical support contracts, goto https://order.mysql.com/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Miguel A. Solórzano [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Mogi das Cruzes - São Paulo, Brazil ___/ www.mysql.com - 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: Upgrading MySQL causes Error - ASP
They replaced your MySQL with a new version. Did they re-compile Apache and PHP to use the new MySQL libraries, or is it trying to use the now missing ones? Celso Pires wrote: Hi there, I've got a site hosted at an ISP and everything was going well when they decided to upgrade the software. Now my site is running under Win2K, IIS5, MySQL 3.23.33 and MyODBC 2.50.36. In order to get easier to explain what is going wrong, I've built the following test: CREATE TABLE person ( person_ID INTEGER NULL, name CHAR(50) NULL, gender CHAR(1) NULL ); INSERT INTO person (person_id, name, gender) values (1,'Bob','m'),(2,'Mary','f'),(3,'Antony','m'),(4,'Rose','f'),(5,'Kuerten','m'); mysql select count(*) as quantity, gender - from person - group by gender; +--++ | quantity | gender | +--++ |2 | f | |3 | m | +--++ 2 rows in set (0.01 sec) *** As you can realize, so far so good. Now things get worse *** html head titleGROUP BY TEST/title /head body bgcolor="#FF" % Response.Write "Beginbr" strConn = "DRIVER=MySQL;SERVER=myserver;DATABASE=mydatabase;UID=myuser;PWD=mypass;" Set conn = Server.Createobject("ADODB.Connection") conn.Open(strConn) strSQL = "select count(*) as quantity, gender " strSQL = strSQL "from person " strSQL = strSQL "group by gender;" Response.Write strSQL "BR" Set Rs = conn.Execute(strSQL) While Not Rs.EOF Response.Write "Quantity: " RS("quantity") " - Gender: " RS("gender") "BR" Rs.MoveNext Wend Rs.Close conn.close response.write "The Endbr" % /body /html *** The page above should print: Begin select count(*) as quantity, gender from person group by gender; Quantity: 2 - Gender: f Quantity: 3 - Gender: m The End *** Instead, I'm getting this: Begin select count(*) as quantity, gender from person group by gender; The End *** It means that the record set is empty. Thank you very much for any help. Regards, Celso. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. - 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 - 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: Upgrading MySQL causes Error - ASP
Gerald, I've written to them asking your question. I'd like to point out that I just got an empty record set when it is running under ASP. The query runs successfully through phpMyAdmin 2.0.5. I realized that the query (select count(*) as quantity from person;) works well in ASP so that I think it should be something related to GROUP BY clause. Celso. - Original Message - From: Gerald L. Clark [EMAIL PROTECTED] To: Celso Pires [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, March 01, 2001 11:11 Subject: Re: Upgrading MySQL causes Error - ASP They replaced your MySQL with a new version. Did they re-compile Apache and PHP to use the new MySQL libraries, or is it trying to use the now missing ones? Celso Pires wrote: Hi there, I've got a site hosted at an ISP and everything was going well when they decided to upgrade the software. Now my site is running under Win2K, IIS5, MySQL 3.23.33 and MyODBC 2.50.36. In order to get easier to explain what is going wrong, I've built the following test: CREATE TABLE person ( person_ID INTEGER NULL, name CHAR(50) NULL, gender CHAR(1) NULL ); INSERT INTO person (person_id, name, gender) values (1,'Bob','m'),(2,'Mary','f'),(3,'Antony','m'),(4,'Rose','f'),(5,'Kuerten','m '); mysql select count(*) as quantity, gender - from person - group by gender; +--++ | quantity | gender | +--++ |2 | f | |3 | m | +--++ 2 rows in set (0.01 sec) *** As you can realize, so far so good. Now things get worse *** html head titleGROUP BY TEST/title /head body bgcolor="#FF" % Response.Write "Beginbr" strConn = "DRIVER=MySQL;SERVER=myserver;DATABASE=mydatabase;UID=myuser;PWD=mypass;" Set conn = Server.Createobject("ADODB.Connection") conn.Open(strConn) strSQL = "select count(*) as quantity, gender " strSQL = strSQL "from person " strSQL = strSQL "group by gender;" Response.Write strSQL "BR" Set Rs = conn.Execute(strSQL) While Not Rs.EOF Response.Write "Quantity: " RS("quantity") " - Gender: " RS("gender") "BR" Rs.MoveNext Wend Rs.Close conn.close response.write "The Endbr" % /body /html *** The page above should print: Begin select count(*) as quantity, gender from person group by gender; Quantity: 2 - Gender: f Quantity: 3 - Gender: m The End *** Instead, I'm getting this: Begin select count(*) as quantity, gender from person group by gender; The End *** It means that the record set is empty. Thank you very much for any help. Regards, Celso. _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. - 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 - 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 - 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