Upgrading rt34 to rt5 database Configurations table missing?

RT Users
1

Trying to upgrade from rt34 to rt5.

Did a pristine installed of rt5

Dumped the rt34 database from the old server.

Restored the rt34 database on the new server and ran the schema upgrade script

rt5$ cd /usr/share/request-tracker5
rt$5 etc/upgrade/upgrade-mysql-schema.pl rt34:192.168.x.x root password > /tmp/queries.sql
rt5$ mysql -h 192.168.x.x -u root -p -v rt34 < /tmp/queries.sql

Tried running some of the etc/upgrade scripts and all of them complain that ‘rt34.Configurations’ doesn’t exist. Command line magic show there is no Configuration table.

MariaDB [rt34]> show tables like 'Configurations%' ;
Empty set (0.001 sec)

Looking in the etc/upgrades I see the Configurations tables is created in 4.5.1/schema.mysql

etc/upgrade# find . -name "*mysql*" | xargs grep -i Configurations
./4.5.1/schema.mysql:CREATE TABLE Configurations (
./4.5.1/schema.mysql:CREATE INDEX Configurations1 ON Configurations (Name, Disabled);
./4.5.1/schema.mysql:CREATE INDEX Configurations2 ON Configurations (Disabled);

I thought the upgrade/upgrade-mysql-schema.pl script would “do the right thing” and CREATE TABLE CONFIGURATION. Did I miss a step? Why didn’t the 4.5.1 schema changes get applied? Below is the queries.sql generated by the upgrade-mysql-schema.pl script

ALTER DATABASE `rt34` DEFAULT CHARACTER SET utf8;
ALTER TABLE ACL
   DEFAULT CHARACTER SET utf8;
ALTER TABLE Attachments
   DEFAULT CHARACTER SET utf8;
ALTER TABLE Attachments
   MODIFY MessageId VARCHAR(160) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Subject VARCHAR(255) CHARACTER SET latin1 NULL DEFAULT NULL,
   MODIFY Filename VARCHAR(255) CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY ContentType VARCHAR(80) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY ContentEncoding VARCHAR(80) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Headers LONGTEXT CHARACTER SET utf8 NULL DEFAULT NULL;
ALTER TABLE Attributes
   DEFAULT CHARACTER SET utf8,
   MODIFY Content BLOB NULL DEFAULT NULL,
   MODIFY ContentType VARBINARY(16) NULL DEFAULT NULL,
   MODIFY ObjectType VARBINARY(64) NULL DEFAULT NULL;
ALTER TABLE Attributes
   MODIFY ContentType VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY ObjectType VARCHAR(64) CHARACTER SET ascii NULL DEFAULT NULL;
ALTER TABLE CustomFields
   DEFAULT CHARACTER SET utf8,
   MODIFY Type VARBINARY(200) NULL DEFAULT NULL,
   MODIFY LookupType VARBINARY(255) NOT NULL DEFAULT '';
ALTER TABLE CustomFields
   MODIFY Type VARCHAR(200) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY LookupType VARCHAR(255) CHARACTER SET ascii NOT NULL DEFAULT '';
ALTER TABLE CustomFieldValues
   DEFAULT CHARACTER SET utf8;
ALTER TABLE GroupMembers
   DEFAULT CHARACTER SET utf8;
ALTER TABLE Groups
   DEFAULT CHARACTER SET utf8,
   MODIFY Domain VARBINARY(64) NULL DEFAULT NULL,
   MODIFY Type VARBINARY(64) NULL DEFAULT NULL;
ALTER TABLE Groups
   MODIFY Domain VARCHAR(64) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Type VARCHAR(64) CHARACTER SET ascii NULL DEFAULT NULL;
ALTER TABLE Links
   DEFAULT CHARACTER SET utf8,
   MODIFY Base VARBINARY(240) NULL DEFAULT NULL,
   MODIFY Target VARBINARY(240) NULL DEFAULT NULL,
   MODIFY Type VARBINARY(20) NOT NULL DEFAULT '';
ALTER TABLE Links
   MODIFY Base VARCHAR(240) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Target VARCHAR(240) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Type VARCHAR(20) CHARACTER SET ascii NOT NULL DEFAULT '';
ALTER TABLE ObjectCustomFields
   DEFAULT CHARACTER SET utf8;
ALTER TABLE ObjectCustomFieldValues
   DEFAULT CHARACTER SET utf8,
   MODIFY ObjectType VARBINARY(255) NOT NULL DEFAULT '',
   MODIFY LargeContent LONGBLOB NULL DEFAULT NULL,
   MODIFY ContentType VARBINARY(80) NULL DEFAULT NULL,
   MODIFY ContentEncoding VARBINARY(80) NULL DEFAULT NULL;
ALTER TABLE ObjectCustomFieldValues
   MODIFY ObjectType VARCHAR(255) CHARACTER SET ascii NOT NULL DEFAULT '',
   MODIFY ContentType VARCHAR(80) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY ContentEncoding VARCHAR(80) CHARACTER SET ascii NULL DEFAULT NULL;
ALTER TABLE Principals
   DEFAULT CHARACTER SET utf8,
   MODIFY PrincipalType VARBINARY(16) NOT NULL DEFAULT '';
ALTER TABLE Principals
   MODIFY PrincipalType VARCHAR(16) CHARACTER SET ascii NOT NULL DEFAULT '';
ALTER TABLE Queues
   DEFAULT CHARACTER SET utf8;
ALTER TABLE ScripActions
   DEFAULT CHARACTER SET utf8,
   MODIFY ExecModule VARBINARY(60) NULL DEFAULT NULL,
   MODIFY Argument VARBINARY(255) NULL DEFAULT NULL;
ALTER TABLE ScripActions
   MODIFY ExecModule VARCHAR(60) CHARACTER SET ascii NULL DEFAULT NULL;
ALTER TABLE ScripConditions
   DEFAULT CHARACTER SET utf8,
   MODIFY ExecModule VARBINARY(60) NULL DEFAULT NULL,
   MODIFY Argument VARBINARY(255) NULL DEFAULT NULL,
   MODIFY ApplicableTransTypes VARBINARY(60) NULL DEFAULT NULL;
ALTER TABLE ScripConditions
   MODIFY ExecModule VARCHAR(60) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY ApplicableTransTypes VARCHAR(60) CHARACTER SET ascii NULL DEFAULT NULL;
ALTER TABLE Scrips
   DEFAULT CHARACTER SET utf8,
   MODIFY Stage VARBINARY(32) NULL DEFAULT NULL;
ALTER TABLE Scrips
   MODIFY Stage VARCHAR(32) CHARACTER SET ascii NULL DEFAULT NULL;
ALTER TABLE sessions
   DEFAULT CHARACTER SET utf8,
   MODIFY id VARBINARY(32) NOT NULL DEFAULT '',
   MODIFY a_session LONGBLOB NULL DEFAULT NULL;
ALTER TABLE Templates
   DEFAULT CHARACTER SET utf8,
   MODIFY Type VARBINARY(16) NULL DEFAULT NULL,
   MODIFY Language VARBINARY(16) NULL DEFAULT NULL;
ALTER TABLE Templates
   MODIFY Type VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Language VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Content TEXT CHARACTER SET utf8 NULL DEFAULT NULL;
ALTER TABLE Tickets
   DEFAULT CHARACTER SET utf8,
   MODIFY Type VARBINARY(16) NULL DEFAULT NULL,
   MODIFY Status VARBINARY(10) NULL DEFAULT NULL;
ALTER TABLE Tickets
   MODIFY Type VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Status VARCHAR(10) CHARACTER SET ascii NULL DEFAULT NULL;
ALTER TABLE Transactions
   DEFAULT CHARACTER SET utf8,
   MODIFY Type VARBINARY(20) NULL DEFAULT NULL,
   MODIFY Field VARBINARY(40) NULL DEFAULT NULL,
   MODIFY ObjectType VARBINARY(64) NOT NULL DEFAULT '',
   MODIFY ReferenceType VARBINARY(255) NULL DEFAULT NULL;
ALTER TABLE Transactions
   MODIFY Type VARCHAR(20) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Field VARCHAR(40) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY ObjectType VARCHAR(64) CHARACTER SET ascii NOT NULL DEFAULT '',
   MODIFY ReferenceType VARCHAR(255) CHARACTER SET ascii NULL DEFAULT NULL;
ALTER TABLE Users
   DEFAULT CHARACTER SET utf8,
   MODIFY Password VARBINARY(40) NULL DEFAULT NULL,
   MODIFY Lang VARBINARY(16) NULL DEFAULT NULL,
   MODIFY Timezone VARBINARY(50) NULL DEFAULT NULL;
ALTER TABLE Users
   MODIFY Comments TEXT CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Signature TEXT CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY FreeformContactInfo TEXT CHARACTER SET utf8 NULL DEFAULT NULL,
   MODIFY Lang VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL,
   MODIFY Timezone VARCHAR(50) CHARACTER SET ascii NULL DEFAULT NULL;
2

I’ve not done a rt3 upgrade, do the docs say to run that command manually?

3

Upgrading from 3.4.5 - #2 by Thomas_Sibley hints that it’s ok to jump from 3.4 to 4.0 I thought I found a post (still trying to find it) that said it was possible to cut from 3.4 to 5.0 but following UPGRADING-x.y documentation but I did not find anything in that documentation about upgrading the schema except running the etc/upgrade/upgrade-mysql-schema.pl script.

MigrateToNewServer - Request Tracker Wiki shows some scripts that may? should? be run when upgrading? I assumed the etc/upgrade/upgrade-mysql-schema.pl would do this?

for action in schema acl insert; do /usr/local/rt/sbin/rt-setup-database --dba root
--dba-password=<password> --action $action --datadir etc/upgrade/3.3.0; done

for action in schema acl insert; do /usr/local/rt/sbin/rt-setup-database --dba root
--dba-password=<password> --action $action --datadir etc/upgrade/3.3.11; done

The question is do you manually need to run the schema changes or is the etc/upgrade/upgrade-mysql-schema.pl supposed to do those schema changes?

4

I use make upgrade-database to perform the upgrade steps, but I am not sure what the lowest version that starts at. You may need to perform some steps manually to get to that lowest version

5

Gonna assume that is from the source deployment of rt? My installation is from the ubuntu packages. Going to need to investigate why the upgrade scripts do not read the rt5 configured database information. Any of the datadir’s I try throw this error message

Type:	SQLite
Host:	localhost
Port:
Name:	/var/lib/request-tracker5/rt5
User:	rt_user
DBA:	root
Failed to connect to dbi:SQLite:dbname=/var/lib/request-tracker5/rt5;host=localhost as user 'root': unable to open database file