We aren’t going about it in a standard way, really. The “upgrade” is being
done on a clean system. The database is the only thing that isn’t going to
be completely fresh, as it will be backed up from the existing system and
imported into MySQL on the new system. I just want to make sure the import
is going to bring everything over in the right manner. From the way it
sounds, I can still run the upgrade on the DB as long as I import it in its
current layout before installation, right?
As for the MySQL 4.1 issues, I’ve seen things regarding the passwords in
4.1. I don’t know a whole lot about this, although documentation I’ve read
for 3.2.2 have also mentioned this as being a problem. I think it may have
been the install notes that accompanied the installation, I really can’t
remember offhand.From: Sheeri Kritzer [mailto:email@example.com]
Sent: Friday, December 03, 2004 2:48 PM
Subject: Re: [rt-users] RT 3.0.2 to 3.2.2 database migration
We’re currently running on 3.0.2, have been since that version came out.
It’s running on MySQL 3.23.58. We’re planning to move to a new system
running RT 3.2.2 and MySQL 4.x. I know there are issues with importing
RT database from an older version into MySQL 4.1. Are there any issues
going from 3.23.x to 4.0.x? Also, are there any tools I need to run to
convert the 3.0.2 database to a 3.2.2 database?
WRT upgrading MySQL, what issues do you ‘know about’? I don’t recall having
issues when I upgraded MySQL.
As well, every installation comes with upgrade instructions. You’ll want to
follow those instructions; they’ll ‘convert’ the database for you. (There
really isn’t a database conversion, just some schema and/or index changes)
University Systems Group