RT2.x -> RT3 (inserting new tickets - internal error)

re

I’m trying to switch from RT 2.0.14 to RT 3.0.4 and I’m having some
difficulties with reimported data from RT2 in new RT3 database. I’m
using postgresql 7.2.1 as database backend on Debian (stable) GNU/Linux
system. I’ve installed RT3 from .debs
(http://people.debian.org/~sjq/debian woody rt3).

I’ve ‘succeded’ with reimporting data with rt2-to-rt3
(rt2-to-rt3-v1.20.tar.gz) utility (yes, I’ve seen some error messages
like this when running dumpfile-ro-rt-3.0 …)

Oct 8 11:22:22 jovanka RT: User n(50) was proposed as a ticket owner
but has no rights to own ticket
s in administracija (/usr/share/perl5/RT/Ticket_Overlay.pm:450)
Oct 8 11:22:23 jovanka RT: Got a deletedticket with a resolved of
Oct 8 11:22:24 jovanka RT: Got a deletedticket with a resolved of
Oct 8 11:22:24 jovanka RT: User n(50) was proposed as a ticket owner
but has no rights to own ticket
s in administracija (/usr/share/perl5//RT/Ticket_Overlay.pm:450)
Oct 8 11:22:28 jovanka RT: Got a deletedticket with a resolved of
Oct 8 09:22:29 jovanka postgres[14413]: [29] ERROR: Invalid UNICODE
character sequence found (0xc84
9)
Oct 8 11:22:29 jovanka RT: DBD::Pg::st execute failed: ERROR: Invalid
UNICODE character sequence fo
und (0xc849) at /usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 410.
(/usr/share/perl5/RT.pm:23
5)
Oct 8 11:22:29 jovanka RT: RT::Handle=HASH(0x8a742bc) couldn’t execute
the query ‘INSERT INTO Attach
ments (Creator, ContentEncoding, Filename, TransactionId, Headers,
ContentType, Subject, Content, id,
Created, Parent) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)’ at
/usr/share/perl5/DBIx/SearchBuilder/H
andle.pm line 417. (/usr/share/perl5//RT.pm:235)

but afterwards when I’ve logged into RT3 all tickets seems to be just
fine. What seems to be the problem at the moment is creating a new
ticket/new que … I got RT Error message:

“Ticket could not be created due to an internal error”

and the RT log file looks like this …

[Wed Oct 8 23:35:22 2003] [warning]: Cannot Encode::Guess; fallback to
iso-8859-1 (/usr/share/perl5/RT/I18N.pm:370)
[Wed Oct 8 23:35:23 2003] [warning]: DBD::Pg::st execute failed:
ERROR: Cannot insert a duplicate key into unique index tickets_pkey at
/usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 410.
(/usr/share/perl5/RT.pm:235)
[Wed Oct 8 23:35:23 2003] [warning]: RT::Handle=HASH(0x89cac40)
couldn’t execute the query ‘INSERT INTO Tickets (Creator, LastUpdated,
Due, Subject, Status, Queue, LastUpdatedBy, Started, Resolved, Owner,
Type, Created, Priority, Starts) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?,
?, ?, ?, ?)’ at /usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 417.
(/usr/share/perl5/RT.pm:235)
[Wed Oct 8 23:35:23 2003] [crit]: Couldn’t create a ticket
(/usr/share/perl5/RT/Ticket_Overlay.pm:512)
[Wed Oct 8 23:35:23 2003] [error]: WebRT: Ticket could not be created
due to an internal error ()
(/usr/share/request-tracker3/html/Elements/Error:54)

Now, I’ve been reading rt-user mailinglist for almost whole day long to
find out what could be wrong with my database. All ‘solutions’ to
similar problem have failed as far as I’ve tested. I’ve also tried with
latest RT (rt 3.0.6) and still the same. So I guess, something must have
get fuckedup in reimporting all the data to new (rt3) Pg database. Does
anyone have a clue, how to fix this.

regards,
Andraz

If you want to travel around the world and be invited to speak at a lot
of different places, just write a Unix operating system.
– Linus Torvalds

a wrote:

ERROR: Cannot insert a duplicate key into unique index tickets_pkey at
/usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 410.

You have to reset postgres’s autoincrements after the import.
This has been discussed several times on rt-users, from
memory.
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances