RT works but still "Almost there" appears

RT Users
1

I have a strange problem. I installed the debian package request-tracker3.4
(using Apache2, MySQL and mod_perl2). RT now works almost. I can login, create
tickets, queues etc., but when I click on ‘Home’ I get the “Almost
there”-message. I can’t see anything in the apache2 logfiles or RT logfile that
could give me a hint on why this is happening, so I hope someone on this list can.
Thanks in advance.

Greetings,
– Pieter van der Spek, pieter@west.nl, West Consulting B.V., +31 15 2191 600

2

Hi all,
I am getting this error while creating a ticket. Has anyone faced such a
problem till now?

[Mon Jun 27 14:27:31 2005] [warning]: DBD::Oracle::st execute failed:
ORA-00001: unique constraint (RT.TICKETS_KEY) violated (DBD ERROR:
OCIStmtExecute) [for Statement “INSERT INTO Tickets (Status, Queue,
Started, Type, InitialPriority, Starts, id, LastUpdated, Subject,
FinalPriority, Creator, Owner, LastUpdatedBy, Resolved, Created, Priority,
Due) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)” with
ParamValues: :p5=‘91’, :p12=‘3919’, :p8=‘2005-06-27 14:27:31’,
:p14=‘1970-01-01 00:00:00’, :p10=‘99’, :p13=‘3919’, :p16=‘91’, :p2=‘54’,
:p3=‘1970-01-01 00:00:00’, :p6=‘1970-01-01 00:00:00’, :p15=‘2005-06-27
14:27:31’, :p1=‘new’, :p7=‘150’, :p17=‘2005-06-28 14:27:31’, :p4=‘ticket’,
:p9=‘Test’, :p11=‘3919’] at
/usr/local/lib/perl5/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line
480, line 105.
(/usr/local/rt/lib/RT.pm:277)
[Mon Jun 27 14:27:31 2005] [warning]: RT::Handle=HASH(0xacb2a50) couldn’t
execute the query ‘INSERT INTO Tickets (Status, Queue, Started, Type,
InitialPriority, Starts, id, LastUpdated, Subject, FinalPriority, Creator,
Owner, LastUpdatedBy, Resolved, Created, Priority, Due) VALUES (?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)’ at
/usr/local/lib/perl5/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line
494, line 105.
(/usr/local/rt/lib/RT.pm:277)
[Mon Jun 27 14:27:31 2005] [crit]: Couldn’t create a ticket: Object could
not be created (/usr/local/rt/lib/RT/Ticket_Overlay.pm:590)

Regards,
Ahalya Nathan
Senior Programmer / Analyst
Information Technology, Metropolitan Utilities District
(402) 449-8218 phone
(402) 449-8131 fax
ahalya_nathan@mudnebr.com

3

At Monday 6/27/2005 10:54 AM, Ahalya_Nathan@mudnebr.com wrote:

Hi all,
I am getting this error while creating a ticket. Has anyone faced such a
problem till now?

[Mon Jun 27 14:27:31 2005] [warning]: DBD::Oracle::st execute failed:
ORA-00001: unique constraint (RT.TICKETS_KEY) violated (DBD ERROR:
OCIStmtExecute) [for Statement "INSERT INTO Tickets

Ahalya,

Sounds like your sequences are messed up - the sequence that’s used to
generate ticket ids needs to be set higher than the highest existing ticket id.

Also, if you have this problem on the tickets table it’s very possible you
have it on other tables too - you should chekc.

Steve

4

At Monday 6/27/2005 03:27 PM, Ahalya_Nathan@mudnebr.com wrote:

The data in the development environment was copied from the production
environment using simple Oracle export/import. The DBA , first truncated
the tables (zeroed them out) then imported with an export file from the RT
system in the production environment. Does this create a problem?

Yes - the sequence is used to generate the primary keys, so must be at
least as high as the highest existing primary key value.

So if after the import, the highest ticket number is 2000, your sequence
must be set to yield at least 2001 the next time it’s used.

And as I mentioned before, there are other tables whose sequences must also
be set - look in the Oracle schema creation file to find what they are. Did
you ask your DBA about this? She/he should be able to get all this
straightened out fairly easily.

Steve

Regards,
Ahalya Nathan
Senior Programmer / Analyst
Information Technology, Metropolitan Utilities District
(402) 449-8218 phone
(402) 449-8131 fax
ahalya_nathan@mudnebr.com

Stephen Turner sturner@MIT.EDU

06/27/2005 01:41 PM
To
Ahalya_Nathan@mudnebr.com
cc
Subject
Re: [rt-users] Issue while creating a ticket

At Monday 6/27/2005 01:33 PM, Ahalya_Nathan@mudnebr.com wrote:

Steve,
“the sequence that’s used to generate ticket ids needs to be set higher
than the highest existing ticket id”.
Do you have to set that in the database or is it handled programatically
in RT?

You have to set it in the database. Did you load data from a migration
script or some other bulk-load method? That might account for how ticket
numbers aren’t synchronized with the sequence.

Steve

Stephen Turner
Senior Programmer/Analyst - Client Support Services
MIT Information Services and Technology (IS&T)