RT database update from 2.0.9 to 3.6.1

Hi all,

I’m stuck in the updating process from RT version 2.0.9 to 3.6.1.

I got RT 3.6.1 up and running on a Mac OS X server. The old RT instance
(2.0.9) is still running on another server. I can’t update the database
with its schema and data on my own! I need some help here please.

The “rt2-to-rt3” database migration tool (mentioned in RT3.2’s readme
file and downloadable at
http://bestpractical.com/pub/rt/devel/rt2-to-rt3.tar.gz) works only from
2.0 to 3.0. My problem is that there are also schema changes between 3.0
and 3.6. I can’t dump my RT2 MySQL database and import it with the tool
mentioned above directly into the RT 3.6 database, can I?

Does this mean i have to do the following “workaround”(??):

 [delete or move my 3.6.1 RT instance ]
  1. install a new RT instance with the version 3.0.
  2. export all the RT2-database data with the “rt2-to-rt3”-tool
  3. import it to the previously installed RT 3.0 software
  4. update the RT software version from 3.0 to 3.6.1 (make upgrade)
  5. update the database (from 3.0 to 3.6.1) with the step-by-step
    schema updates for the updates within 3.x.x (located at
    /path/to/rt-3.6.1/etc/upgrade/)

After reading through wiki.bestpractical.com, this mailing list and the
readme files this seems to be the only way to do it :-(. I hope someone
found an easier way?!

Thanks in advance.
T. Koch

---- SWITCH - The Swiss Education & Research Network ----
Thomas Koch; SWITCH; Postfach; CH-8021 Zurich; Switzerland
thomas.koch@switch.ch; +41 442681586; fax: +41 442681568

The “rt2-to-rt3” database migration tool (mentioned in RT3.2’s
readme file and downloadable at http://bestpractical.com/pub/rt/
devel/rt2-to-rt3.tar.gz) works only from 2.0 to 3.0. My problem is
that there are also schema changes between 3.0 and 3.6. I can’t
dump my RT2 MySQL database and import it with the tool mentioned
above directly into the RT 3.6 database, can I?

Thomas

There has been recent customer work on this tool, but it is only
available in subversion. We’d love to hear if it works for you. You
can find the code here:

svn://svn.bestpractical.com/rt2-to-rt3/trunk

-kevin

Hi Kevin

What kind of “customer work” do you mean? What is new to the tool?
Update from 2.x.x to 3.6.x?

I will give this subversion a try and let you know whether it works for
me or not.

Thanks a lot!

Thomas

Kevin Falcone wrote:

Dear Kevin and list

Using the rt2-to-rt3 update software I experienced some problems with
the mail attachments. All the attachments in the RT 3.6 Database are
unreadable now!

Error message copied from my browser:

The image �http://rt.switch.ch/Ticket/Attachment/52274/20897/nichch.png�
cannot be displayed, because it contains errors.

There must be a problem in the export or import of all the tickets.

Can anybody help me?

Thanks in advance.

Thomas

Thomas Koch wrote:

Hi Kevin

What kind of “customer work” do you mean? What is new to the tool?
Update from 2.x.x to 3.6.x?

I will give this subversion a try and let you know whether it works for
me or not.

Thanks a lot!


Thomas

Kevin Falcone wrote:

The “rt2-to-rt3” database migration tool (mentioned in RT3.2’s
readme file and downloadable at
http://bestpractical.com/pub/rt/devel/rt2-to-rt3.tar.gz) works only
from 2.0 to 3.0. My problem is that there are also schema changes
between 3.0 and 3.6. I can’t dump my RT2 MySQL database and import it
with the tool mentioned above directly into the RT 3.6 database, can I?

Thomas

There has been recent customer work on this tool, but it is only
available in subversion. We’d love to hear if it works for you. You
can find the code here:

svn://svn.bestpractical.com/rt2-to-rt3/trunk

-kevin

---- SWITCH - The Swiss Education & Research Network ----
Thomas Koch; SWITCH; Postfach; CH-8021 Zurich; Switzerland
thomas.koch@switch.ch; +41 442681586; fax: +41 442681568

Using the rt2-to-rt3 update software I experienced some problems
with the mail attachments. All the attachments in the RT 3.6
Database are unreadable now!

There was a problem with base64 encoded attachments.
It has been fixed in subversion, r6761

Let me know if that fixes it for you

-kevin