Schema of the mysql-database suitable to RT 4.0.5

Please keep list mail on the list.On Fri, Apr 20, 2012 at 09:36:39AM +0200, Joerg Hollandmoritz wrote:

As I mentioned already we have a fresh installation of RT 4.0.5. with
only importing data from a former version. This was handled via
mysql-export at the old version (3.6.3) and mysql-import in the new
version (phpmyadmin).
Then I made the following:
" root@ultra:/opt/helpdesk.tmp# make upgrade-database
/usr/bin/perl -I/opt/helpdesk/local/lib -I/opt/helpdesk/lib
sbin/rt-setup-database --action upgrade --prompt-for-dba-password
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as root
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: DV_rt
User: dvATmysql
DBA: root
Enter RT version you’re upgrading from: 4.0.5
The version 4.0.5 you’re upgrading to is up to date.
Done. "

How can I see the version of the schema of the mysql-database?
How can I get the mysql-database properly running with RT ?

The command asked what version you’re upgrading from, which you say is
3.6.3. You’ll need to enter that at the prompt. You’ll also
need to read and follow all other upgrade steps in docs/UPGRADING 3.6
3.8 and 4.0 as well as paying particular attention to
docs/UPGRADING.mysql

-kevin

Hi!

I created a new database; then I imported the data from a former
version. After that I made all the updates (schema,…) like described
below.
make upgrade-database
· upgrading from 3.6.3 =>
/usr/bin/perl -I/opt/helpdesk/local/lib -I/opt/helpdesk/lib
sbin/rt-setup-database --action upgrade --prompt-for-dba-password
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as root
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: DV_rt
User: dvATmysql
DBA: root
Enter RT version you’re upgrading from: 3.6.3
No DB changes since 3.6.3.
Done.

The RT 4.0.5 seems to be working, but two problems persist:

  1. The user root possesses the password
    root 3134336162623631346331366434373832623763613966303536646135663463
    After looging in the password changed

to 21736861353132214952642f71666a37334a427153414a5a2149626b534f507850704669786c6b38
{it’s not usable}

  1. When I wanted to change the owner of a ticket I get the message:
    “Ergebnisse * Konnte Besitzer nicht ändern:”
    [Can’t change owner]

The access-log says:
ip.ip.ip.ip - - [23/Apr/2012:11:53:37 +0200] “GET
/Ticket/ModifyAll.html?id=18895 HTTP/1.1” 200 7340
ip.ip.ip.ip - - [23/Apr/2012:11:53:50 +0200] “POST
/Ticket/ModifyAll.html HTTP/1.1” 200 7458

Can you give me some hints ?

Best

George

Am Fr 20.04.2012 15:04 schrieb Kevin Falcone
falcone@bestpractical.com:

Hi!

I created a new database; then I imported the data from a former
version. After that I made all the updates (schema,…) like described
below.
make upgrade-database
· upgrading from 3.6.3 =>


/usr/bin/perl -I/opt/helpdesk/local/lib -I/opt/helpdesk/lib
sbin/rt-setup-database --action upgrade --prompt-for-dba-password
In order to create or update your RT database, this script needs to
connect to your mysql instance on localhost as root
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: DV_rt
User: dvATmysql
DBA: root
Enter RT version you’re upgrading from: 3.6.3
No DB changes since 3.6.3.

This is wrong, there are a ton of changes since 3.6.3.
Where are you running the command from? You’re support to run it from
the unpacked RT tarball.

Your selects below demonstrate that the length of the password field
is still insufficient.

You also don’t appear to have run any of the other upgrade steps
between 3.6 and 4.0 that I pointed out in my earlier email, this
includes a vitally important characterset change between 3.6 and 3.8.
I’ve called out the note from before:

need to read and follow all other upgrade steps in docs/UPGRADING 3.6
3.8 and 4.0 as well as paying particular attention to
docs/UPGRADING.mysql

You may find the blog post on upgrading useful

-kevin