Problems updating to RT 3.8.0

I must be missing something obvious, but I’m trying to set up a test
RT instance where I can practice what I’m going to do with my upgrade
procedure (from RT 3.4.2).

So far, I’ve built a brand new RT 3.8.0 installation, which works
fine. My plan, at this stage, was going to be to drop the RT
database, load a database dump from my production instance, and then
apply the patches as described in the README and UPGRADING.mysql
files. My understanding is that I need to apply the schema patches in
etc/upgrade first, and then apply the mysql 4.0-4.1 patch, correct?

The problem is I seem to have fallen at the first hurdle. With my
current directory the location in which I unpacked the RT 3.8 tarball,
I try to apply the 3.5.1 patch, which is the lowest number higher than
the current RT version I’m using, and I get this:

/itch/rt-3.8.0/sbin/rt-setup-database --action schema --datadir etc/

upgrade/3.5.1
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as rtuser
Please specify that user’s database password below. If the user has no
database
password, just press return.

Password:
Working with:
Type: mysql
Host: localhost
Name: rtdb
User: rtuser
DBA: rtuser
Now populating database schema.
Couldn’t finish ‘schema’ step.

ERROR: Couldn’t find schema file(s) ‘*’

There doesn’t seem to be anything except a file called ‘content’ in
that etc/upgrade/3.5.1 - is that correct?

Thanks for your help, I feel like I must have missed something really
obvious here…

Tim

The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.

Tim Cutts-2 wrote:

/itch/rt-3.8.0/sbin/rt-setup-database --action schema --datadir etc/

upgrade/3.5.1
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as rtuser
Please specify that user’s database password below. If the user has no
database
password, just press return.

I think you probably got the datadir wrong. Try
/itch/rt-3.8.0/etc/upgrade/3.5.1 as the datadir.

View this message in context: http://www.nabble.com/Problems-updating-to-RT-3.8.0-tp18508882p18509377.html

Many thanks for your reply.On 17 Jul 2008, at 3:13 pm, bertbat wrote:

Tim Cutts-2 wrote:

/itch/rt-3.8.0/sbin/rt-setup-database --action schema --datadir

etc/
upgrade/3.5.1
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as rtuser
Please specify that user’s database password below. If the user has
no
database
password, just press return.

I think you probably got the datadir wrong. Try
/itch/rt-3.8.0/etc/upgrade/3.5.1 as the datadir.

Nope, still doesn’t work. The upgrade dirs are where I initially
unpacked the software:

ls /itch/rt-3.8.0-tmp/etc/upgrade

3.1.0 3.7.1 3.7.82 3.8-ical-extension
3.1.15 3.7.10 3.7.85 3.8-ical-extension.in
3.1.17 3.7.15 3.7.86 3.8.0
3.3.0 3.7.19 3.7.87 schema.mysql-4.0-4.1.pl
3.3.11 3.7.3 3.8-branded-queues-extension shrink_cgm_table.pl
3.5.1 3.7.81 3.8-branded-queues-extension.in

So they’re all there. Now, when I try to apply them, with the full
path this time:

/itch/rt-3.8.0/sbin/rt-setup-database --action schema --datadir /

itch/rt-3.8.0-tmp/etc/upgrade/3.5.1
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as rtuser
Please specify that user’s database password below. If the user has no
database
password, just press return.

Password:
Working with:
Type: mysql
Host: localhost
Name: rtdb
User: rtuser
DBA: rtuser
Now populating database schema.
Couldn’t finish ‘schema’ step.

ERROR: Couldn’t find schema file(s) ‘*’

I’ve now run the script through the perl debugger, and it’s looking
for files in the patch datadir called ‘schema’ or ‘schema.mysql’.
There’s no such file. Is it expected that in some patches there’s no
schema change? I sort of figured there had to be one for 3.5.1 for
the changes in the UI that happened in RT 3.6. If it is OK that
it’s not there, then should I just proceed with the next steps, even
though it’s reported this error?

Tim

The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.

Tim Cutts-2 wrote:

I’ve now run the script through the perl debugger, and it’s looking
for files in the patch datadir called ‘schema’ or ‘schema.mysql’.
There’s no such file. Is it expected that in some patches there’s no
schema change? I sort of figured there had to be one for 3.5.1 for
the changes in the UI that happened in RT 3.6. If it is OK that
it’s not there, then should I just proceed with the next steps, even
though it’s reported this error?

There are quite a few schema.mysql-files, but there seems to be none in
3.5.1, so I’d just continue with the next step. Also, what did the job for
me was to use the -upgrade option instead of doing all steps manually.

/opt/rt3/sbin/rt-setup-database --dba user --prompt-for-dba-password
–action upgrade

View this message in context: http://www.nabble.com/Problems-updating-to-RT-3.8.0-tp18508882p18510327.html

Tim Cutts-2 wrote:

I’ve now run the script through the perl debugger, and it’s looking
for files in the patch datadir called ‘schema’ or ‘schema.mysql’.
There’s no such file. Is it expected that in some patches there’s no
schema change? I sort of figured there had to be one for 3.5.1 for
the changes in the UI that happened in RT 3.6. If it is OK that
it’s not there, then should I just proceed with the next steps, even
though it’s reported this error?

There are quite a few schema.mysql-files, but there seems to be none
in
3.5.1, so I’d just continue with the next step. Also, what did the
job for
me was to use the -upgrade option instead of doing all steps manually.

/opt/rt3/sbin/rt-setup-database --dba user --prompt-for-dba-password
–action upgrade

Aha! That version worked fine! Thanks!

Tim

The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.

A followup report: the mysql 4.0-4.1 upgrade program failed with the
following error:

DBD::mysql::db column_info failed: column_info doesn’t support column
selection at etc/upgrade/schema.mysql-4.0-4.1.pl

I had been using DBD::mysql 3.0008. Updating to 4.007 allowed the
script to work. So it might be an idea to add a version check on
DBD::mysql to schema.mysql-4.0-4.1.pl

Tim

The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.