Migrating RT DB from mysql 4.1.11 to 5.0.51

Hello we are running RT for our company’s day to day request handling, and customer center issue logging.
We want to migrate RT DB to a new machine (newer OS and new mysql version).
But facing the problems due to the big DB size and table encodings.

Our RT system info:

RT version: 3.4.1
Mysql: 4.1.11-Debian_4sarge2-log
OS: debian 3.1
RT DB size: 27G

Problem description can be found here:
http://bugs.mysql.com/bug.php?id=44953

Did anyone experienced similar situation and if yes what was the solution if any.

Thanks,
Arnas Kupsys

Have you looked into UPGRADING.mysql file that is shipped with RT 3.8?On Tue, May 19, 2009 at 5:40 PM, Arnas.Kupsys@swisscom.com wrote:

Hello we are running RT for our company’s day to day request handling, and customer center issue logging.
We want to migrate RT DB to a new machine (newer OS and new mysql version).
But facing the problems due to the big DB size and table encodings.

Our RT system info:

RT version: 3.4.1
Mysql: 4.1.11-Debian_4sarge2-log
OS: debian 3.1
RT DB size: 27G

Problem description can be found here:
http://bugs.mysql.com/bug.php?id=44953

Did anyone experienced similar situation and if yes what was the solution if any.

Thanks,
Arnas Kupsys


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Best regards, Ruslan.

Hello we are running RT for our company’s day to day request handling, and customer center issue logging.
We want to migrate RT DB to a new machine (newer OS and new mysql version).
But facing the problems due to the big DB size and table encodings.

We recently upgraded from Postgres 8.0 (or 8.1 I don’t recall which)
to 8.3, which had stricted UTF-8 checking, and we had to manually go
in and fix up all the UTF-8 errors that were allowed to creep in. It
was painful, but scripting it helped a lot… :slight_smile:

It sounds really like you have a mysql bug. It seems the correct
forum for you is where you filed your bug report.

We already look into the perl script to migrate to utf8.

Arnas-----Original Message-----
From: rt-devel-bounces@lists.bestpractical.com [mailto:rt-devel-bounces@lists.bestpractical.com] On Behalf Of Vick Khera
Sent: Wednesday, May 20, 2009 4:24 PM
To: rt-devel@lists.bestpractical.com
Subject: Re: [Rt-devel] Migrating RT DB from mysql 4.1.11 to 5.0.51

On Tue, May 19, 2009 at 5:40 PM, Arnas.Kupsys@swisscom.com wrote:

Hello we are running RT for our company’s day to day request handling, and customer center issue logging.
We want to migrate RT DB to a new machine (newer OS and new mysql version).
But facing the problems due to the big DB size and table encodings.

We recently upgraded from Postgres 8.0 (or 8.1 I don’t recall which) to 8.3, which had stricted UTF-8 checking, and we had to manually go in and fix up all the UTF-8 errors that were allowed to creep in. It was painful, but scripting it helped a lot… :slight_smile:

It sounds really like you have a mysql bug. It seems the correct forum for you is where you filed your bug report.
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Don’t dump it using latin1, but use binary:
–default-character-set=binary . If dump still fails then it’s totally
mysql problem.On Wed, May 20, 2009 at 7:16 PM, Arnas.Kupsys@swisscom.com wrote:

We already look into the perl script to migrate to utf8.

Arnas

-----Original Message-----
From: rt-devel-bounces@lists.bestpractical.com [mailto:rt-devel-bounces@lists.bestpractical.com] On Behalf Of Vick Khera
Sent: Wednesday, May 20, 2009 4:24 PM
To: rt-devel@lists.bestpractical.com
Subject: Re: [Rt-devel] Migrating RT DB from mysql 4.1.11 to 5.0.51

On Tue, May 19, 2009 at 5:40 PM, Arnas.Kupsys@swisscom.com wrote:

Hello we are running RT for our company’s day to day request handling, and customer center issue logging.
We want to migrate RT DB to a new machine (newer OS and new mysql version).
But facing the problems due to the big DB size and table encodings.

We recently upgraded from Postgres 8.0 (or 8.1 I don’t recall which) to 8.3, which had stricted UTF-8 checking, and we had to manually go in and fix up all the UTF-8 errors that were allowed to creep in. It was painful, but scripting it helped a lot… :slight_smile:

It sounds really like you have a mysql bug. It seems the correct forum for you is where you filed your bug report.


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel


List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Best regards, Ruslan.