[rt-users] rt2tort3 import errors

[Dominic Hargreaves]

Hi,

I'm working through the migration of our relatively large RT2 data
set (500,000 tickets) with rt2tort3.

I've already fixed a number of issues with the scripts and I plan to
submit anything relevant as patches once I've had a chance to get
through it all, but there are a couple of things I've hit that I
don't understand.

I've managed a complete export and import cycle okay, and I'm now
testing the incremental mode (which will be required to get the
migration done without excessive downtime). Most tickets are getting
apparently imported succesfully but this one barfs:

Previously this was prefixed with an error (that may have been
incidentally exposed) regarding the now-defunct TicketCustomFieldValues
table. I've now fixed the import script to use use the
ObjectCustomFieldValues instead, and just get:

(queue name and subject name elided)

t-1395038: w[Tue Nov  3 15:36:51 2009] [crit]: Couldn't set EffectiveId: That is already the current value (/usr/share/request-tracker3.8/lib/RT/Ticket_Overlay.pm:500)

Couldn't create TICKET: Ticket could not be created due to an internal error$VAR1 = {
          'Status' => 'resolved',
          'Queue' => 'xxxx',
          'Started' => '2009-10-12 15:12:59+00',
          'Starts' => '1970-01-01 00:00:00+00',
          '_RecordTransaction' => '0',
          'id' => '1395038',
          'LastUpdated' => '2009-10-12 15:13:00+00',
          'Requestor' => [
                         '132522'
                       ],
          'Subject' => 'xxxx',
          'Creator' => undef,
          'Owner' => undef,
          'LastUpdatedBy' => undef,
          'EffectiveId' => '1395038',
          'Resolved' => '2009-10-12 15:12:59+00',
          'Created' => '2009-09-27 18:07:14+00',
          'Due' => '2009-09-27 18:07:14+00'
        };
[Tue Nov  3 15:36:51 2009] [crit]: Died at ./dumpfile-to-rt-3.0 line 700. (/usr/share/request-tracker3.8/lib/RT.pm:387)
Died at ./dumpfile-to-rt-3.0 line 700.

I'm completely failing to make any sense of the error here:

Couldn't set EffectiveId: That is already the current value

since this ticket, which has Id == EffectiveId, is like most other
tickets in this regard, so I can't see even see what's unusual about
this ticket to trigger the bug.

The second problem that I've not completely sorted out is that
most of the ticket imports spew:

[Tue Nov  3 14:40:08 2009] [warning]: Use of uninitialized value $MIMEType in pattern match (m//) at /usr/share/request-tracker3.8/lib/RT/Record.pm line 736. (/usr/share/request-tracker3.8/lib/RT/Record.pm:736)
[Tue Nov  3 14:40:08 2009] [warning]: Use of uninitialized value $Body in length at /usr/share/request-tracker3.8/lib/RT/Record.pm line 753. (/usr/share/request-tracker3.8/lib/RT/Record.pm:753)
[Tue Nov  3 14:40:08 2009] [warning]: Use of uninitialized value in subroutine entry at /usr/share/request-tracker3.8/lib/RT/Record.pm line 783. (/usr/share/request-tracker3.8/lib/RT/Record.pm:783)

I've already squelched a couple of further uninitialized value warnings
in dumpfile-to-rt3.0 itself (on $a->{'ContentEncoding'}) but I'm not
sure of the *correct* way to fix these cases (I could just default it
to an empty string but that doesn't seem right, really).

Any insights or hints would be most appreciated.

Versions, etc:

Live RT2 install: Debian sarge, postgres 7.4
RT2 migrate install: Debian lenny, postgres 7.4 (with suitably old
DBIx::SearchBuilder etc)
RT3 test install: Debian lenny, postgres 8.3, RT 3.8.5 (haven't moved
to 3.8.6 yet as I wanted to complete one round of testing beforehand).

Thanks,
Dominic.

-- 
Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford