[rt-users] Upgrading to RT 3.6.1 from RT 3.4.1 and 3.0.11 with older MySql versions on them.

[Mathew Snyder]

You're stuck doing the upgrade.  Each revision introduces new aspects to 
the database schema that need to be integrated smoothly in order to make 
everything work well.  It isn't that big a process.  Simply import the 
database onto the new machine's instance of MySQL and run 'make upgrade' 
for 3.6.1.  It will update the schema to the proper settings for use 
with the newer version.  The same can be done for 3.4.1.

By trying other methods you are creating more work than will be done by 
simply running the upgrade in the first place.

Mathew Snyder

Farrell,Bob wrote:
> All,
> 
>  I have two machines that I want to move to RT 3.6.1, on new machines 
> running MySql 5.0.22-1.
> 
> Both units have MySql 4.0.18 on them.
> 
> The RT machine with RT 3.4.1 imported just fine.
> 
> The RT Machine with 3.0.11 did not.
> 
> I built a standalone NEW box without issue.
> 
> I understand this maybe a MySql issue, and no fault of RT, but was 
> wondering if anyone had any ideas that could assist me.
> 
> The mysql dump from 3.4.1 was a simple mysql dump to a “backup.sql” file 
> and imported fine.
> 
> The 3.0.11 mysql dump gave me table “rt3.atrribute missing” in the logs 
> when bringing up the RT interface after login, and I could not navigate 
> anywhere, although I did see the queues in the drop down menu.
> 
> Any MySql gurus out there that may have run across this before?
> 
> I added the attribute table, and now can see ALL tickets, etc, but no 
> comments /data /email correspondence in them under the History section. 
> I also get “an internal error has occurred” when creating a ticket in 
> the RT 3.0.11 to 3.6.1 box, but the ticket does in fact get created. ( 
> still won’t fly with the admins though )
> 
> A requirement of this facility that uses RT 3.0.11 is that all History, 
> time worked, etc. is retained in the migration. I am hoping to use the 
> existing Rt3.0.11 mysql dumps and move the data, not go the upgrade 
> mysql revision by revision route. Could this be repaired via an RT 
> setting, or am I stuck in mysql upgrade land ?
> 
> Or perhaps a person has an idea I have not even thought of.
> 
> Any help would be greatly appreciated.
> 
> Kudos to Jesse Vincent and the Team, as the new box, and the 3.4.1 
> upgrade are working flawlessly !
> 
> Thanks
> 
> Bob
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> 
> 
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
> Buy a copy at http://rtbook.bestpractical.com