<br><br><div class="gmail_quote">On Tue, Nov 18, 2008 at 6:33 AM, Tim Cutts <span dir="ltr"><<a href="mailto:tjrc@sanger.ac.uk">tjrc@sanger.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
On 17 Nov 2008, at 10:34 pm, Asif Iqbal wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap<br>
somewhere?<br>
</blockquote>
<br></div>
You can do this in almost one go, yes. It's almost exactly what I'm doing with my production RT, where I'm going from 3.4.2 to 3.8.1<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Do I upgrade the mysql 4.0.24 to 4.1 first before upgrading the RT?<br>
</blockquote>
<br></div>
Yes. Or at least, here's what I've tested, and seems to work quite well:<br>
<br>
1) Set up a new RT box for your new server, so that you can always back out if this goes wrong. On this server, install the new version of MySQL you want to use, and install RT 3.8.1<br>
<br>
2) Make a dump of your production MySQL instance, and load it into the new MySQL database.<br>
<br>
3) Run the /opt/rt3/sbin/rt-setup-database --action upgrade command as detailed in the RT 3.8.1 README file, but only as far as version 3.8.0<br>
<br>
4) Run the MySQL upgrade script, as detailed in UPGRADING.mysql, and apply the SQL statements it wants you to make. This can take a long time; the alter table statements are pretty slow-running.<br>
<br>
5) Run the /opt/rt3/sbin/rt-setup-database --action upgrade thing again for the last small changes from 3.8.0 to 3.8.1</blockquote><div><br>On my new server (not production yet) the upgrade is failing. I don't want to change the ACL on<br>
the database unless that is harmless, to successfully upgrade<br><br>/opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade<br>In order to create or update your RT database, this script needs to connect to your mysql instance on localhost as root<br>
Please specify that user's database password below. If the user has no database<br>password, just press return.<br><br>Password: <br>Working with:<br>Type: mysql<br>Host: localhost<br>Name: rt3<br>User: rt_user<br>
DBA: root<br>Enter RT version you're upgrading from: 3.4.5<br><br>Going to apply following upgrades:<br>* 3.5.1<br>* 3.7.1<br>* 3.7.3<br>* 3.7.10<br>* 3.7.15<br>* 3.7.19<br>* 3.7.81<br>* 3.7.82<br>* 3.7.85<br>* 3.7.86<br>
* 3.7.87<br>* 3.8.0<br>* 3.8.1<br>* 3.8.2<br><br>Enter RT version if you want to stop upgrade at some point,<br> or leave it blank if you want apply above upgrades: <br><br>IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP<br>
<br>Proceed [y/N]:y<br>Processing 3.5.1<br>DBI connect('dbname=rt3;host=localhost','rt_user',...) failed: Access denied for user 'rt_user'@'localhost' (using password: YES) at /opt/csw/share/perl/site_perl/DBIx/SearchBuilder/Handle.pm line 106<br>
Connect Failed Access denied for user 'rt_user'@'localhost' (using password: YES)<br> at /opt/rt3/sbin/../lib/RT.pm line 204<br><br><br>I can login OK with `mysql -u root -p rt3' <br>I failed to login with `mysql -u rt_user -p rt3' using the password I have in RT_*Config.pm files (same) for rt_user<br>
<br>The same login attempt works on the original instance of RT (3.4.5) <br><br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
After that, it all seemed to work pretty well.<br>
<br>
Tim<br><font color="#888888">
<br>
<br>
-- <br>
The Wellcome Trust Sanger Institute is operated by Genome ResearchLimited, a charity registered in England with number 1021457 and acompany registered in England with number 2742969, whose registeredoffice is 215 Euston Road, London, NW1 2BE.<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Asif Iqbal<br>PGP Key: 0xE62693C5 KeyServer: <a href="http://pgp.mit.edu">pgp.mit.edu</a><br>A: Because it messes up the order in which people normally read text.<br>
Q: Why is top-posting such a bad thing?<br><br><br>