I'm moving RT to a new server and taking the opportunity to upgrade versions as well.
Currently, v3.6.3 on FC4 and MySql 4.1.16. I backed up the db with Mysqldump --opt --add-drop-table --single-transaction -default-character-set=binary -u root -pXXXXXXX rt3 >rt363.adhoc.bkup Copied the SQL dump to the new server running CentOS 5.5 and MySql 5.0.77 and restored the RT3 db. Last week, I successfully upgraded from 3.6.3 to 3.8.9 (patched the db to 3.7.87, applied the 3.8.0 schema changes, patched the database up to 3.8.9 as per UPGRADING.mysql). Worked great, no problems. Was just about to implement that when RT 4.0.0 was released... So....I want to upgrade to that instead. There was no UPGRADING.mysql, just the README saying to run rt-setup-database. When I try to upgrade from 3.6.3 all the way up to 4.0.0, I'm getting: Processing 3.7.81 Now populating database schema. [Mon May 2 20:53:58 2011] [crit]: DBD::mysql::st execute failed: Duplicate key name 'CachedGroupMembers3' at /opt/rt4/sbin/../lib/RT/Handle.pm line 503. (/opt/rt4/sbin/../lib/RT.pm:340) DBD::mysql::st execute failed: Duplicate key name 'CachedGroupMembers3' at /opt/rt4/sbin/../lib/RT/Handle.pm line 503. Since the 3.8.9 upgrade worked fine (with the included schema change queries), I used rt3.8.9 to upgrade my 3.6.3 to 3.8.9 (again, going to 3.7.87, applying the schema change queries, then upgrading the db to 3.8.9). Which, again, worked fine. Then, using RT 4.0.0, I tried to update the database from 3.8.9 to 4.0.0 and am getting the error: Processing 3.9.3 Now populating database schema. [Mon May 2 20:31:51 2011] [crit]: DBD::mysql::st execute failed: Can't DROP 'DelegatedBy'; check that column/key exists at /opt/rt4/sbin/../lib/RT/Handle.pm line 503. (/opt/rt4/sbin/../lib/RT.pm:340) DBD::mysql::st execute failed: Can't DROP 'DelegatedBy'; check that column/key exists at /opt/rt4/sbin/../lib/RT/Handle.pm line 503. Do I need to upgrade incrementally from 3.6.3 to 3.8.9 to 3.9.x and then to 4.0.0? Is there info on this that I missed? Or, should the rt-setup-database handle the jump from 3.6.3 to 4.0.0 (including 3.8.0's schema changes)? (I'm not a SQL expert in the least). Thanks for any help! Steve
