[rt-users] RT 3.4.1 upgrade oddness?

[Rich West]

After some testing, we upgraded our main Request Tracker server from 
3.2.2 to 3.4.1 and we were very pleased with the results: it went 
extremely smooth and there was little to no interruption of service.

So, with that nice experience under our belt, we took on the task of 
upgrading on of our clients' installations of Request Tracker from 3.2.2 
(we keep the versions in sync for ease of maintenance) to 3.4.1 and, 
well, this upgrade didn't go as smoothly.  One of the upgrade scripts 
(3.3.0 - schema) generated an error, but we pressed onwards.

However, now, we are seeing the following in the error_log, and 
transaction body entries are not making it in to the database:
[Tue Mar 15 14:38:47 2005] [error] [client 67.160.250.30] FastCGI: 
server "/opt/rt3/bin/mason_handler.fcgi" stderr: 
RT::Handle=HASH(0xa6bc66c) couldn't execute the query 'SELECT DISTINCT 
main.Id AS id, main.Filename AS filename, main.ContentType AS 
contenttype, main.Headers AS headers, main.Subject AS subject, 
main.Parent AS parent, main.ContentEncoding AS contentencoding, 
main.ContentType AS contenttype, main.TransactionId AS transactionid, 
main.Created AS created FROM Attachments main , Transactions 
Transactions_1, Tickets Tickets_2  WHERE ((Tickets_2.EffectiveId = 
'12557')) AND ((Transactions_1.Ticket = Tickets_2.id)) AND 
((main.TransactionId = Transactions_1.id)) ' at 
/usr/lib/perl5/site_perl/5.8.3/DBIx/SearchBuilder/Handle.pm line 494., 
referer: 
http://site.org/Ticket/Update.html?Action=Comment&DefaultStatus=resolved&id=12557
[Tue Mar 15 14:38:47 2005] [error] [client 67.160.250.30] FastCGI: 
server "/opt/rt3/bin/mason_handler.fcgi" stderr: DBD::mysql::st execute 
failed: Unknown column 'Transactions_1.Ticket' in 'where clause' at 
/usr/lib/perl5/site_perl/5.8.3/DBIx/SearchBuilder/Handle.pm line 480., 
referer: 
http://site.org/Ticket/Update.html?Action=Comment&DefaultStatus=resolved&id=12557

I know a fair amount of SQL, but , after looking at the database and 
getting completely lost with the aliases (Transactions_1, Tickets_2) 
stuff, I figured I would toss the question out to the list to see if 
anyone has an idea as to what is going on, what failed, and what I might 
do to fix this?

I compared the working version of 3.4.1 with this problematic version 
and I cannot see any column differences.  There just isn't a 
transactions.ticket in either instance. :(

Thanks!
-Rich

-- 
Richard West               $14.95 Registrations    mailto:rwest at wesmo.com
Wesmo Computer Services    .com .net .org .tv .cc  http://www.wesmo.com
Full Domain & Web Hosting  .BIZ .INFO & MORE!!