[rt-users] Database upgrade from 3.4.5 to 3.7.87 fails with Unkown Column

[Ken Johnson]

I'm trying to upgrade from RT 3.4.5 to 4.0.7 on Debian 6.0.7.

I backed up the existing database and loaded it a new database according the
the instructions in UPGRADING.mysql.  I reached the point where I believed
it was time to perform the first stage of the database upgrades, and used a
command like this:

rt-setup-database-4 --action upgrade --dba user --dba-password password


Here's what I saw:

Working with:
Type:	mysql
Host:	localhost
Name:	/var/lib/dbconfig-common/sqlite3/request-tracker4/rtdb
User:	
DBA:	user
Enter RT version you're upgrading from: 3.4.5

Going to apply following upgrades:
* 3.5.1
* ... 
* 4.0.6

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

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

IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP

Proceed [y/N]:y
Processing 3.5.1
Now inserting data.
Processing 3.7.1
Now inserting data.
Processing 3.7.3
Now populating database schema.
[Fri Apr  5 21:40:38 2013] [crit]: DBD::mysql::st execute failed: Unknown
column 'Pattern' in 'CustomFields' at
/usr/share/request-tracker4/lib/RT/Handle.pm line 515.
(/usr/share/request-tracker4/lib/RT.pm:351)
DBD::mysql::st execute failed: Unknown column 'Pattern' in 'CustomFields' at
/usr/share/request-tracker4/lib/RT/Handle.pm line 515.

So I thought that perhaps there was some bogus column in the old database:

mysql> use rt3
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables;
+-------------------------+
| Tables_in_rt3           |
+-------------------------+
| ACL                     |
| Attachments             |
| Attributes              |
| CachedGroupMembers      |
| CustomFieldValues       |
| CustomFields            |
| GroupMembers            |
| Groups                  |
| Links                   |
| ObjectCustomFieldValues |
| ObjectCustomFields      |
| Principals              |
| Queues                  |
| ScripActions            |
| ScripConditions         |
| Scrips                  |
| Templates               |
| TicketCustomFieldValues |
| Tickets                 |
| Transactions            |
| Users                   |
| sessions                |
+-------------------------+
22 rows in set (0.00 sec)ysql> describe CustomFields;
+---------------+--------------+------+-----+---------+----------------+
| Field         | Type         | Null | Key | Default | Extra          |
+---------------+--------------+------+-----+---------+----------------+
| id            | int(11)      | NO   | PRI | NULL    | auto_increment |
| Name          | varchar(200) | YES  |     | NULL    |                |
| Type          | varchar(200) | YES  |     | NULL    |                |
| Queue         | int(11)      | NO   |     | 0       |                |
| Description   | varchar(255) | YES  |     | NULL    |                |
| SortOrder     | int(11)      | NO   |     | 0       |                |
| Creator       | int(11)      | NO   |     | 0       |                |
| Created       | datetime     | YES  |     | NULL    |                |
| LastUpdatedBy | int(11)      | NO   |     | 0       |                |
| LastUpdated   | datetime     | YES  |     | NULL    |                |
| Disabled      | smallint(6)  | NO   | MUL | 0       |                |
+---------------+--------------+------+-----+---------+----------------+
11 rows in set (0.00 sec)

I don't see that column in that table in the original database.

Can anyone point me in the right direction?

Ken