Re: 3.23.58 - 5.0.22 upgrade
Dan Buettner wrote: Dan T - Well, if all your data files are MyISAM, then I only see one potential problem, and that is the area of user permissions. I believe that things in that area have changed around enough that if you simply re-use those tables as-is (as-are?), you may have some difficulties. All your other databases with .frm, .MYD, and .MYI files - should be fine. The MyISAM engine itself hasn't changed (to my knowledge) since 3.23. Those files are platform-agnostic and re-usable by different versions of MySQL. I once moved a set of 3.23.x files on OS X to a Linux box running 4.0 without trouble. Also went from OS X to Solaris, though with same MySQL verison. Just put the files in the proper data directory, and mind the filesystem permissions. For safety's sake use copies not originals. As to the MySQL permission problems you may have - I'd recommend using the included mysql_fix_privilege_tables script (in bin directory on my 5.0 install). Says it updates the privilege tables to comply with 4.0 and above. Also mind the new password hashing in 4.1 and 5.x; you can enable the old passwords, but you have to explicitly do so. HTH, Dan On 7/18/06, Martin Jespersen [EMAIL PROTECTED] wrote: Hi - Well, I've been trying a few things with this, however I can't quite seem to get to the point where this would be any easier. The problem is, I only have data files. I don't have a MySQL dump, and don't see myself being able to grab a dump anytime soon. So I guess what I'm faced with now is bringing up a 3.23.58 server anyway, if only for the purpose of a massive MySQL dump. How's that sound? Thanks! -dant HI - Just to update... I actually did do the upgrade path suggested by dev.mysql.com. It worked, and worked well. I think using RPMs for this made the job a hell of a lot easier, too. Anyway, I just wanted to follow up, hopefully this will help someone in the future. Thanks -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 3.23.58 - 5.0.22 upgrade
Martin Jespersen wrote: Dan has a very good point, be mindfull of the changed password algorithm, that actually was a bit of a bother to me since i have tons of users defined in my grant tables. Dan Buettner wrote: Dan, I wouldn't bother with the intermediate steps (4.0, 4.1) . Waste of time (fine products, but you say you want to go to 5.0). I'd go direct to 5.0, using mysqldump'd data as Martin did. If you're all-MyISAM then it might also work to simply upgrade your binaries and keep your data files, though you'll want to watch for the fix permissions script and also be mindful of the password changes that came about with 4.1. Dan On 7/13/06, Martin Jespersen [EMAIL PROTECTED] wrote: I recently upgraded from 3.23.58 - 4.1.20 without any hickups. I simply dumped my databases with mysqldump on the 3.23.58 installation and imported them again from inside the mysql client by using the source command. Dan Trainor wrote: Hi - I know we've rolled this around the list a few times, but I was wondering if there's been any real development on the subject lately. I know half of you are saying Forget it... go with a newer version and get over it, and I'd really really like to, but i have a lot of data store under 3.23.x. The documentation says that you must follow 3 - 4.0 - 4.1 - 5.0 ... ..., and that's just what I'm about to do. I guess what I'm looking for here is some advice from people who have done it. If there's not an all-in-one silly stupid way to upgrade the data in this manner (i.e. with one fell swoop of some handy dandy application), would someone on an RPM-based system simply upgrade RPMs in sequential order as indicated, and hope that the data follows? Is this probably one of the more successful ways of doing this? I'm still exploring my options, but I think that's what I'm going to end up going with here - one step at a time. If you guys wouldn't mind terribly talking about this for a few more posts, I (and hopefully others) would greatly appreciate it. Thanks for the time -dant -- Hi - Well, I've been trying a few things with this, however I can't quite seem to get to the point where this would be any easier. The problem is, I only have data files. I don't have a MySQL dump, and don't see myself being able to grab a dump anytime soon. So I guess what I'm faced with now is bringing up a 3.23.58 server anyway, if only for the purpose of a massive MySQL dump. How's that sound? Thanks! -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 3.23.58 - 5.0.22 upgrade
Using dumps are almost always the way to go, upgrading the datafiles themselves is something you should avoid unless you are into heavy wizardry and/or pain. Dan Trainor wrote: Martin Jespersen wrote: Dan has a very good point, be mindfull of the changed password algorithm, that actually was a bit of a bother to me since i have tons of users defined in my grant tables. Dan Buettner wrote: Dan, I wouldn't bother with the intermediate steps (4.0, 4.1) . Waste of time (fine products, but you say you want to go to 5.0). I'd go direct to 5.0, using mysqldump'd data as Martin did. If you're all-MyISAM then it might also work to simply upgrade your binaries and keep your data files, though you'll want to watch for the fix permissions script and also be mindful of the password changes that came about with 4.1. Dan On 7/13/06, Martin Jespersen [EMAIL PROTECTED] wrote: I recently upgraded from 3.23.58 - 4.1.20 without any hickups. I simply dumped my databases with mysqldump on the 3.23.58 installation and imported them again from inside the mysql client by using the source command. Dan Trainor wrote: Hi - I know we've rolled this around the list a few times, but I was wondering if there's been any real development on the subject lately. I know half of you are saying Forget it... go with a newer version and get over it, and I'd really really like to, but i have a lot of data store under 3.23.x. The documentation says that you must follow 3 - 4.0 - 4.1 - 5.0 ... ..., and that's just what I'm about to do. I guess what I'm looking for here is some advice from people who have done it. If there's not an all-in-one silly stupid way to upgrade the data in this manner (i.e. with one fell swoop of some handy dandy application), would someone on an RPM-based system simply upgrade RPMs in sequential order as indicated, and hope that the data follows? Is this probably one of the more successful ways of doing this? I'm still exploring my options, but I think that's what I'm going to end up going with here - one step at a time. If you guys wouldn't mind terribly talking about this for a few more posts, I (and hopefully others) would greatly appreciate it. Thanks for the time -dant -- Hi - Well, I've been trying a few things with this, however I can't quite seem to get to the point where this would be any easier. The problem is, I only have data files. I don't have a MySQL dump, and don't see myself being able to grab a dump anytime soon. So I guess what I'm faced with now is bringing up a 3.23.58 server anyway, if only for the purpose of a massive MySQL dump. How's that sound? Thanks! -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 3.23.58 - 5.0.22 upgrade
Dan T - Well, if all your data files are MyISAM, then I only see one potential problem, and that is the area of user permissions. I believe that things in that area have changed around enough that if you simply re-use those tables as-is (as-are?), you may have some difficulties. All your other databases with .frm, .MYD, and .MYI files - should be fine. The MyISAM engine itself hasn't changed (to my knowledge) since 3.23. Those files are platform-agnostic and re-usable by different versions of MySQL. I once moved a set of 3.23.x files on OS X to a Linux box running 4.0 without trouble. Also went from OS X to Solaris, though with same MySQL verison. Just put the files in the proper data directory, and mind the filesystem permissions. For safety's sake use copies not originals. As to the MySQL permission problems you may have - I'd recommend using the included mysql_fix_privilege_tables script (in bin directory on my 5.0 install). Says it updates the privilege tables to comply with 4.0 and above. Also mind the new password hashing in 4.1 and 5.x; you can enable the old passwords, but you have to explicitly do so. HTH, Dan On 7/18/06, Martin Jespersen [EMAIL PROTECTED] wrote: Hi - Well, I've been trying a few things with this, however I can't quite seem to get to the point where this would be any easier. The problem is, I only have data files. I don't have a MySQL dump, and don't see myself being able to grab a dump anytime soon. So I guess what I'm faced with now is bringing up a 3.23.58 server anyway, if only for the purpose of a massive MySQL dump. How's that sound? Thanks! -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 3.23.58 - 5.0.22 upgrade
On 7/13/06, Dan Trainor [EMAIL PROTECTED] wrote: Martin Jespersen wrote: Dan has a very good point, be mindfull of the changed password algorithm, that actually was a bit of a bother to me since i have tons of users defined in my grant tables. Dan Buettner wrote: Dan, I wouldn't bother with the intermediate steps (4.0, 4.1) . Waste of time (fine products, but you say you want to go to 5.0). I'd go direct to 5.0, using mysqldump'd data as Martin did. If you're all-MyISAM then it might also work to simply upgrade your binaries and keep your data files, though you'll want to watch for the fix permissions script and also be mindful of the password changes that came about with 4.1. Dan On 7/13/06, Martin Jespersen [EMAIL PROTECTED] wrote: I recently upgraded from 3.23.58 - 4.1.20 without any hickups. I simply dumped my databases with mysqldump on the 3.23.58 installation and imported them again from inside the mysql client by using the source command. Dan Trainor wrote: Hi - I know we've rolled this around the list a few times, but I was wondering if there's been any real development on the subject lately. I know half of you are saying Forget it... go with a newer version and get over it, and I'd really really like to, but i have a lot of data store under 3.23.x. The documentation says that you must follow 3 - 4.0 - 4.1 - 5.0 ... ..., and that's just what I'm about to do. I guess what I'm looking for here is some advice from people who have done it. If there's not an all-in-one silly stupid way to upgrade the data in this manner (i.e. with one fell swoop of some handy dandy application), would someone on an RPM-based system simply upgrade RPMs in sequential order as indicated, and hope that the data follows? Is this probably one of the more successful ways of doing this? I'm still exploring my options, but I think that's what I'm going to end up going with here - one step at a time. If you guys wouldn't mind terribly talking about this for a few more posts, I (and hopefully others) would greatly appreciate it. Thanks for the time -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Hi - Thanks, both of you, for your replies. Like I said, I've experienced problems in the past with a mysqldump between major version changes. Maybe it's just my luck, or maybe it's a hit-or-miss from big jumps, I'm not entirely sure. So did I. I recommend (always) to follow the devs advice at the docs, to migrate to each major version, check everything and go on. There were MAJOR changes, password, grant table, new fields, old fields renamed, specially at the mysql database. Its not THAT hard, and instead of a waste of time, it may be gain of time as you may encounter serious errors when going directly to 5 from 3. No matter what others say, I had a pretty good fight with grant table, users, permissions, passwords and some data lost in fields in a migration directly, wich was easily fixed with scripts provided by mysql specially for each major version change. Right now, most of my data is InnoDB. As I believe Martin pointed out (or maybe not... someone from [EMAIL PROTECTED]), be wary of transactions, which I can overwrite using an import switch. I was able to actually convert to 5.0.22 directly from 3.23.58, and I'm having my devs mow through the data to see if it all works as designed. They are having trouble with passwords, but they're fixing that on a case-by-case basis, which is fine with us. I'll keep you guys posted regardless. It seems that this subject pops up a lot with conflicting answers, so I'd like to give everyone else as much information about the process as I can. Thanks again, much appreciated. -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- 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]
3.23.58 - 5.0.22 upgrade
Hi - I know we've rolled this around the list a few times, but I was wondering if there's been any real development on the subject lately. I know half of you are saying Forget it... go with a newer version and get over it, and I'd really really like to, but i have a lot of data store under 3.23.x. The documentation says that you must follow 3 - 4.0 - 4.1 - 5.0 ... ..., and that's just what I'm about to do. I guess what I'm looking for here is some advice from people who have done it. If there's not an all-in-one silly stupid way to upgrade the data in this manner (i.e. with one fell swoop of some handy dandy application), would someone on an RPM-based system simply upgrade RPMs in sequential order as indicated, and hope that the data follows? Is this probably one of the more successful ways of doing this? I'm still exploring my options, but I think that's what I'm going to end up going with here - one step at a time. If you guys wouldn't mind terribly talking about this for a few more posts, I (and hopefully others) would greatly appreciate it. Thanks for the time -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 3.23.58 - 5.0.22 upgrade
I recently upgraded from 3.23.58 - 4.1.20 without any hickups. I simply dumped my databases with mysqldump on the 3.23.58 installation and imported them again from inside the mysql client by using the source command. Dan Trainor wrote: Hi - I know we've rolled this around the list a few times, but I was wondering if there's been any real development on the subject lately. I know half of you are saying Forget it... go with a newer version and get over it, and I'd really really like to, but i have a lot of data store under 3.23.x. The documentation says that you must follow 3 - 4.0 - 4.1 - 5.0 ... ..., and that's just what I'm about to do. I guess what I'm looking for here is some advice from people who have done it. If there's not an all-in-one silly stupid way to upgrade the data in this manner (i.e. with one fell swoop of some handy dandy application), would someone on an RPM-based system simply upgrade RPMs in sequential order as indicated, and hope that the data follows? Is this probably one of the more successful ways of doing this? I'm still exploring my options, but I think that's what I'm going to end up going with here - one step at a time. If you guys wouldn't mind terribly talking about this for a few more posts, I (and hopefully others) would greatly appreciate it. Thanks for the time -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: 3.23.58 - 5.0.22 upgrade
Dan, I wouldn't bother with the intermediate steps (4.0, 4.1) . Waste of time (fine products, but you say you want to go to 5.0). I'd go direct to 5.0, using mysqldump'd data as Martin did. If you're all-MyISAM then it might also work to simply upgrade your binaries and keep your data files, though you'll want to watch for the fix permissions script and also be mindful of the password changes that came about with 4.1. Dan On 7/13/06, Martin Jespersen [EMAIL PROTECTED] wrote: I recently upgraded from 3.23.58 - 4.1.20 without any hickups. I simply dumped my databases with mysqldump on the 3.23.58 installation and imported them again from inside the mysql client by using the source command. Dan Trainor wrote: Hi - I know we've rolled this around the list a few times, but I was wondering if there's been any real development on the subject lately. I know half of you are saying Forget it... go with a newer version and get over it, and I'd really really like to, but i have a lot of data store under 3.23.x. The documentation says that you must follow 3 - 4.0 - 4.1 - 5.0 ... ..., and that's just what I'm about to do. I guess what I'm looking for here is some advice from people who have done it. If there's not an all-in-one silly stupid way to upgrade the data in this manner (i.e. with one fell swoop of some handy dandy application), would someone on an RPM-based system simply upgrade RPMs in sequential order as indicated, and hope that the data follows? Is this probably one of the more successful ways of doing this? I'm still exploring my options, but I think that's what I'm going to end up going with here - one step at a time. If you guys wouldn't mind terribly talking about this for a few more posts, I (and hopefully others) would greatly appreciate it. Thanks for the time -dant -- 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: 3.23.58 - 5.0.22 upgrade
Dan has a very good point, be mindfull of the changed password algorithm, that actually was a bit of a bother to me since i have tons of users defined in my grant tables. Dan Buettner wrote: Dan, I wouldn't bother with the intermediate steps (4.0, 4.1) . Waste of time (fine products, but you say you want to go to 5.0). I'd go direct to 5.0, using mysqldump'd data as Martin did. If you're all-MyISAM then it might also work to simply upgrade your binaries and keep your data files, though you'll want to watch for the fix permissions script and also be mindful of the password changes that came about with 4.1. Dan On 7/13/06, Martin Jespersen [EMAIL PROTECTED] wrote: I recently upgraded from 3.23.58 - 4.1.20 without any hickups. I simply dumped my databases with mysqldump on the 3.23.58 installation and imported them again from inside the mysql client by using the source command. Dan Trainor wrote: Hi - I know we've rolled this around the list a few times, but I was wondering if there's been any real development on the subject lately. I know half of you are saying Forget it... go with a newer version and get over it, and I'd really really like to, but i have a lot of data store under 3.23.x. The documentation says that you must follow 3 - 4.0 - 4.1 - 5.0 ... ..., and that's just what I'm about to do. I guess what I'm looking for here is some advice from people who have done it. If there's not an all-in-one silly stupid way to upgrade the data in this manner (i.e. with one fell swoop of some handy dandy application), would someone on an RPM-based system simply upgrade RPMs in sequential order as indicated, and hope that the data follows? Is this probably one of the more successful ways of doing this? I'm still exploring my options, but I think that's what I'm going to end up going with here - one step at a time. If you guys wouldn't mind terribly talking about this for a few more posts, I (and hopefully others) would greatly appreciate it. Thanks for the time -dant -- 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: 3.23.58 - 5.0.22 upgrade
Martin Jespersen wrote: Dan has a very good point, be mindfull of the changed password algorithm, that actually was a bit of a bother to me since i have tons of users defined in my grant tables. Dan Buettner wrote: Dan, I wouldn't bother with the intermediate steps (4.0, 4.1) . Waste of time (fine products, but you say you want to go to 5.0). I'd go direct to 5.0, using mysqldump'd data as Martin did. If you're all-MyISAM then it might also work to simply upgrade your binaries and keep your data files, though you'll want to watch for the fix permissions script and also be mindful of the password changes that came about with 4.1. Dan On 7/13/06, Martin Jespersen [EMAIL PROTECTED] wrote: I recently upgraded from 3.23.58 - 4.1.20 without any hickups. I simply dumped my databases with mysqldump on the 3.23.58 installation and imported them again from inside the mysql client by using the source command. Dan Trainor wrote: Hi - I know we've rolled this around the list a few times, but I was wondering if there's been any real development on the subject lately. I know half of you are saying Forget it... go with a newer version and get over it, and I'd really really like to, but i have a lot of data store under 3.23.x. The documentation says that you must follow 3 - 4.0 - 4.1 - 5.0 ... ..., and that's just what I'm about to do. I guess what I'm looking for here is some advice from people who have done it. If there's not an all-in-one silly stupid way to upgrade the data in this manner (i.e. with one fell swoop of some handy dandy application), would someone on an RPM-based system simply upgrade RPMs in sequential order as indicated, and hope that the data follows? Is this probably one of the more successful ways of doing this? I'm still exploring my options, but I think that's what I'm going to end up going with here - one step at a time. If you guys wouldn't mind terribly talking about this for a few more posts, I (and hopefully others) would greatly appreciate it. Thanks for the time -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] Hi - Thanks, both of you, for your replies. Like I said, I've experienced problems in the past with a mysqldump between major version changes. Maybe it's just my luck, or maybe it's a hit-or-miss from big jumps, I'm not entirely sure. Right now, most of my data is InnoDB. As I believe Martin pointed out (or maybe not... someone from [EMAIL PROTECTED]), be wary of transactions, which I can overwrite using an import switch. I was able to actually convert to 5.0.22 directly from 3.23.58, and I'm having my devs mow through the data to see if it all works as designed. They are having trouble with passwords, but they're fixing that on a case-by-case basis, which is fine with us. I'll keep you guys posted regardless. It seems that this subject pops up a lot with conflicting answers, so I'd like to give everyone else as much information about the process as I can. Thanks again, much appreciated. -dant -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
