<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>All,<o:p></o:p></p>
<p class=MsoNormal> I have two machines that I want to move to RT 3.6.1, on new
machines running MySql 5.0.22-1.<o:p></o:p></p>
<p class=MsoNormal>Both units have MySql 4.0.18 on them.<o:p></o:p></p>
<p class=MsoNormal>The RT machine with RT 3.4.1 imported just fine.<o:p></o:p></p>
<p class=MsoNormal>The RT Machine with 3.0.11 did not.<o:p></o:p></p>
<p class=MsoNormal>I built a standalone NEW box without issue.<o:p></o:p></p>
<p class=MsoNormal>I understand this maybe a MySql issue, and no fault of RT,
but was wondering if anyone had any ideas that could assist me.<o:p></o:p></p>
<p class=MsoNormal>The mysql dump from 3.4.1 was a simple mysql dump to a
“backup.sql” file and imported fine.<o:p></o:p></p>
<p class=MsoNormal>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.<o:p></o:p></p>
<p class=MsoNormal>Any MySql gurus out there that may have run across this
before?<o:p></o:p></p>
<p class=MsoNormal>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 )<o:p></o:p></p>
<p class=MsoNormal>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 ?<o:p></o:p></p>
<p class=MsoNormal>Or perhaps a person has an idea I have not even thought of.<o:p></o:p></p>
<p class=MsoNormal>Any help would be greatly appreciated.<o:p></o:p></p>
<p class=MsoNormal>Kudos to Jesse Vincent and the Team, as the new box, and the
3.4.1 upgrade are working flawlessly !<o:p></o:p></p>
<p class=MsoNormal>Thanks<o:p></o:p></p>
<p class=MsoNormal>Bob<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>