Can't upgrade db from 2.x to 3.x

RT Users
1

When trying to follow the directions to upgrade the database on an RT 3.0.0
install with postgres 7.3.2, I do and get this:

[root@support rt-3-0-0]# /usr/sbin/rt-setup-database --action
insert --datafile
etc/upgrade/2-1-71
Creating Superuser ACL…Can’t locate etc/upgrade/2-1-71 in @INC (@INC
contains
: /usr/local/rt3/lib /usr/lib/perl5/5.6.1/i386-linux /usr/lib/perl5/5.6.1
/usr/l
ib/perl5/site_perl/5.6.1/i386-linux /usr/lib/perl5/site_perl/5.6.1
/usr/lib/perl
5/site_perl/5.6.0/i386-linux /usr/lib/perl5/site_perl/5.6.0
/usr/lib/perl5/site_
perl /usr/lib/perl5/vendor_perl/5.6.1/i386-linux
/usr/lib/perl5/vendor_perl/5.6.
1 /usr/lib/perl5/vendor_perl .) at /usr/sbin/rt-setup-database line 339.

Then I tried an absolute path:

[root@support rt-3-0-0]# /usr/sbin/rt-setup-database --action
insert --datafile
/home/jon/rt-3-0-0/etc/upgrade/2-1-71
Creating Superuser ACL…Can’t locate /home/jon/rt-3-0-0/etc/upgrade/2-1-71
at
/usr/sbin/rt-setup-database line 339.

the file is there…and I checked perms along the path…I can’t see why
this isn’t working…could someone please clue me in?

smime.p7s (2.79 KB)

2

-----BEGIN PGP SIGNED MESSAGE-----

On 04-Apr-2003, Jonathan Mischo wrote message “[rt-users] Can’t upgrade db from
2.x to 3.x”

When trying to follow the directions to upgrade the database on an RT 3.0.0
install with postgres 7.3.2, I do and get this:

[root@support rt-3-0-0]# /usr/sbin/rt-setup-database --action
insert --datafile

Did you try just doing ‘make initialize-database’?

Andy Harrison
Great Works Internet
System Operations
(full headers for details)

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQCVAwUBPo3pKlPEkLgodAWVAQF7rgQArXWgbjjh6rtYQfA+edccKcNmXwcQPuk1
AWX7lnEpYBTC8jbJp3/jmke0YYDc+7rxh2Aqrdy5NbVTbIsz+CCW6LVT1E9KnR79
jYF+uSrIlYiOV95Wl6AQb/AIJGjRlnfKShvVzn/4DFMDLgv6d50y9EJQkVEX8v9B
ZhQm289c3GA=
=tNbC
-----END PGP SIGNATURE-----

3

When trying to follow the directions to upgrade the database on an RT
3.0.0
install with postgres 7.3.2, I do and get this:

[root@support rt-3-0-0]# /usr/sbin/rt-setup-database --action
insert --datafile

Did you try just doing ‘make initialize-database’?

I don’t want to lose my existing setup, that’s why I’m trying to upgrade the
db format, instead of starting from scratch.

4

If you’re moving from RT 2.0.x to RT 3.0.x you want the rt2-to-rt3 tool
from http://fsck.com/pub/rt/devel/On Fri, Apr 04, 2003 at 03:09:27PM -0600, Jonathan Mischo wrote:

When trying to follow the directions to upgrade the database on an RT
3.0.0
install with postgres 7.3.2, I do and get this:

[root@support rt-3-0-0]# /usr/sbin/rt-setup-database --action
insert --datafile

Did you try just doing ‘make initialize-database’?

I don’t want to lose my existing setup, that’s why I’m trying to upgrade the
db format, instead of starting from scratch.

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

5

If you’re moving from RT 2.0.x to RT 3.0.x you want the rt2-to-rt3 tool
from http://fsck.com/pub/rt/devel/

[jon@support rt2-to-rt3]$ ./rt-2.0-to-dumpfile rt2dump
“LoadConfig” is not exported by the RT::Interface::CLI module at
./rt-2.0-to-dumpfile line 32
“DBConnect” is not exported by the RT::Interface::CLI module at
./rt-2.0-to-dumpfile line 32
Can’t continue after import errors at ./rt-2.0-to-dumpfile line 32
BEGIN failed–compilation aborted at ./rt-2.0-to-dumpfile line 32.

As you can see, this doesn’t work, either…and I followed the
directions…I’m inches away from sacrificing my whole db…but that’s
REALLY not high on my list…upgrading shouldn’t have to be this hard.