[rt-users] RT Database Upgrade 3.4.5 -> 3.8.6

[Simon Liang]

Hi guys,

We've upgraded to 3.8.5 with no problems, but however upgrading the database is a different story:

**********************************************************
rt3:~/rt-3.8.6# mysql -u rt_upgrader -p -h 10.2.0.63 rt3_upgrade2
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 529971
Server version: 5.0.26-Debian_3-log Debian etch distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> exit
Bye
rt3:~/rt-3.8.6# pwd
/root/rt-3.8.6
rt3:~/rt-3.8.6# /root/rt-3.8.6/sbin/rt-setup-database --dba rt_upgrader --action upgrade
In order to create or update your RT database, this script needs to connect to your  SQLite instance on 10.2.0.63 as rt_upgrader
Please specify that user's database password below. If the user has no database
password, just press return.

Password:
Working with:
Type:   SQLite
Host:   10.2.0.63
Name:   rt3_upgrade2
User:   rt_upgrader
DBA:    rt_upgrader
Enter RT version you're upgrading from: 3.4.5

Going to apply following upgrades:
* 3.5.1
* 3.7.1
* 3.7.3
* 3.7.10
* 3.7.15
* 3.7.19
* 3.7.81
* 3.7.82
* 3.7.85
* 3.7.86
* 3.7.87
* 3.8.0
* 3.8.1
* 3.8.2
* 3.8.3
* 3.8.4
* 3.8.6

Enter RT version if you want to stop upgrade at some point,
  or leave it blank if you want apply above upgrades:

IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP

Proceed [y/N]:y
Processing 3.5.1
DBI connect('dbname=/root/rt-3.8.6/var/rt3_upgrade2;host=10.2.0.63','rt_upgrader',...) failed: unable to open database file at /usr/local/share/perl/5.8.8/DBIx/SearchBuilder/Handle.pm line 108
Connect Failed unable to open database file
 at /root/rt-3.8.6/sbin/../lib/RT.pm line 204
**********************************************************

Why is the dbname "/root/rt-3.8.6/var/rt3_upgrade2"? Not too sure why it's not working... thanks in advance for any help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20100511/5c9665b3/attachment.htm>