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 the
RT database from an older version into MySQL 4.1. Are there any issues with
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?

Thanks,

Mike Frazer
Web Production Support Specialist
iPAY - A Pay By Touch Company
E-Mail: mike.frazer@ipay.com

Quoting Mike.Frazer@ipay.com:

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 the
RT database from an older version into MySQL 4.1. Are there any issues with
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 any
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)

-Sheeri Kritzer
Systems Administrator
University Systems Group
Tufts University
617-627-3925
sheeri.kritzer@tufts.edu

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:sheeri.kritzer@tufts.edu]
Sent: Friday, December 03, 2004 2:48 PM
To: Mike.Frazer@ipay.com
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] RT 3.0.2 to 3.2.2 database migration

Quoting Mike.Frazer@ipay.com:

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
the
RT database from an older version into MySQL 4.1. Are there any issues
with
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
any
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)

-Sheeri Kritzer
Systems Administrator
University Systems Group
Tufts University
617-627-3925
sheeri.kritzer@tufts.edu

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-
bounces@lists.bestpractical.com] On Behalf Of Mike.Frazer@ipay.com
Sent: Friday, December 03, 2004 12:33 PM
To: sheeri.kritzer@tufts.edu; Mike.Frazer@ipay.com
Cc: rt-users@lists.bestpractical.com
Subject: RE: [rt-users] RT 3.0.2 to 3.2.2 database migration

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.

http://dev.mysql.com/doc/mysql/en/Old_client.html

There’s a new encryption method for passwords in 4.1.

Mike

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQbEMIpzgx7Y34AxGEQIWlgCdHeWVa/jVV/lpUIN+TLzh9mTg7LwAoL2q
YDYQxyp/oIJa1NFt56LxBYRx
=CT0v
-----END PGP SIGNATURE-----

Is this not an RT issue then? I know RT was using a Base64-encoded MD5
hash, and I was unaware that it was using any internal MySQL functions to
derive this password.From: Michael Smith [mailto:mksmith@noanet.net]
Sent: Friday, December 03, 2004 8:00 PM
To: Mike.Frazer@ipay.com; sheeri.kritzer@tufts.edu
Cc: rt-users@lists.bestpractical.com
Subject: RE: [rt-users] RT 3.0.2 to 3.2.2 database migration

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-
bounces@lists.bestpractical.com] On Behalf Of Mike.Frazer@ipay.com
Sent: Friday, December 03, 2004 12:33 PM
To: sheeri.kritzer@tufts.edu; Mike.Frazer@ipay.com
Cc: rt-users@lists.bestpractical.com
Subject: RE: [rt-users] RT 3.0.2 to 3.2.2 database migration

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.

http://dev.mysql.com/doc/mysql/en/Old_client.html

There’s a new encryption method for passwords in 4.1.

Mike

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQbEMIpzgx7Y34AxGEQIWlgCdHeWVa/jVV/lpUIN+TLzh9mTg7LwAoL2q
YDYQxyp/oIJa1NFt56LxBYRx
=CT0v
-----END PGP SIGNATURE-----