Hi,
I made some experiments migrating the db of my existing rt 4.21 installation from mysql to postgres.
I did the following.
-
rt-validator —check —resolve until I got no errormessages anymore
-
rt-serializer —clone —page 200 —directory /my/backup/directory
-
rt—import /my/backup/directory
I found out the following:
-
rt-serializer and rt-import are not installed automatically, had to copy them from my build directory manually to the RTs sbin directory
-
the import fails, as it is expecting the .dat files not in /my/backup/directory but in /my/backup/directory//my/backup/directory
adding a symbolic link works as a workarround but this seems to be a bug. Not using the —directory switch works as well.
- the import fails right at the beginning with
DBD::Pg::st execute failed: ERROR: relation “users” does not exist
LINE 1: SELECT * FROM Users WHERE LOWER(Name) = LOWER($1)
Any ideas?
Matthias
I found out the following:
- rt-serializer and rt-import are not installed automatically, had to
copy them from my build directory manually to the RTs sbin directory
Already fixed in 4.2.2rc1.
- the import fails, as it is expecting the .dat files not in
/my/backup/directory but in /my/backup/directory//my/backup/directory
adding a symbolic link works as a workarround but this seems to be a
bug. Not using the —directory switch works as well.
Looks like a bug, yes. File it on issues.bestpractical.com?
- the import fails right at the beginning with
DBD::Pg::st execute failed: ERROR: relation “users” does not exist
LINE 1: SELECT * FROM Users WHERE LOWER(Name) = LOWER($1)
http://docs.bestpractical.com/rt-importer#CLONED_DATA
Hi,
thanks for the quick response,
after
sbin/rt-setup-database --action create,schema,acl --prompt-for-dba-password
the import went flawlessly,
MatthiasAm 12.01.2014 um 21:24 schrieb Alex Vandiver alexmv@bestpractical.com:
On Sun, 2014-01-12 at 20:42 +0100, Matthias Peplow wrote:
I found out the following:
- rt-serializer and rt-import are not installed automatically, had to
copy them from my build directory manually to the RTs sbin directory
Already fixed in 4.2.2rc1.
- the import fails, as it is expecting the .dat files not in
/my/backup/directory but in /my/backup/directory//my/backup/directory
adding a symbolic link works as a workarround but this seems to be a
bug. Not using the —directory switch works as well.
Looks like a bug, yes. File it on issues.bestpractical.com?
- the import fails right at the beginning with
DBD::Pg::st execute failed: ERROR: relation “users” does not exist
LINE 1: SELECT * FROM Users WHERE LOWER(Name) = LOWER($1)
http://docs.bestpractical.com/rt-importer#CLONED_DATA