Error running rt2-to-rt3 upgrade

Can anyone tell me why some of the dumpfile script’s attempts to import some
ticket transactions is failing? I put the pertinent information below. If
I should provide something else, please let me know.

I just attempted to upgrade from RT2 to RT3, following the README. When
running:

./dumpfile-to-rt3 rt2dump

It would error out at this line of the dumpfile script in import_tickets (I
added the DEBUG stuff so that it would keep going):

unless ( $trans_obj->Id == $t->{‘id’} ) {
open DEBUG, “>>/tmp/rt3-foo”;
print DEBUG "Couldn’t create trans " . $t->{‘id’} . “\n” .
Dumper($t);
close DEBUG;
#exit;
}

This error occurred on 1,478 tickets out of a total of 23,498. Basically,
the end result was that the ticket was imported, but missing some history.

When I looked at a particular errored transaction, I could not find a reason
why it would have caused a problem:
Couldn’t create trans 140427
$VAR1 = {
‘OldValue’ => ‘10’,
‘Type’ => ‘Give’,
‘Field’ => ‘Owner’,
‘Ticket’ => ‘20718’,
‘Created’ => ‘2004-12-31 00:04:28’,
‘id’ => 140427,
‘NewValue’ => ‘1698’,
‘Creator’ => ‘1698’,
‘ActivateScrips’ => ‘0’
};

RT2 Database Entry:
mysql> select * from Transactions where Ticket=‘20718’;
| id | EffectiveTicket | Ticket | TimeTaken | Type | Field | OldValue
| NewValue | Data | Creator | Created |
| 130616 | NULL | 20718 | 0 | Create | NULL | NULL
| NULL | NULL | 5 | 2004-10-29 03:04:29 |
| 140426 | NULL | 20718 | 0 | Status | Status | new
| resolved | NULL | 5 | 2004-12-31 00:04:28 |
| 140427 | NULL | 20718 | 0 | Give | Owner | 2
| 5 | NULL | 5 | 2004-12-31 00:04:28 |
3 rows in set (0.00 sec)

RT3 Imported Version of the ticket:
mysql> select * from Transactions where ObjectId=‘20718’ AND
ObjectType=‘RT::Ticket’;
| id | ObjectType | ObjectId | TimeTaken | Type | Field | OldValue |
NewValue | ReferenceType | OldReference | NewReference | Data | Creator |
Created |
| 130616 | RT::Ticket | 20718 | 0 | Create | NULL | NULL |
NULL | NULL | NULL | NULL | | 1698 |
2004-10-29 03:04:29 |
1 row in set (0.00 sec)

One more try…

Can anyone tell me why some of the dumpfile script’s attempts to
import some ticket transactions is failing? I put the pertinent
information below. If I should provide something else, please let
me know.

I just attempted to upgrade from RT2 to RT3, following the README.
When running:

./dumpfile-to-rt3 rt2dump

It would error out at this line of the dumpfile script in
import_tickets (I added the DEBUG stuff so that it would keep
going):

unless ( $trans_obj->Id == $t->{‘id’} ) {
open DEBUG, “>>/tmp/rt3-foo”;
print DEBUG "Couldn’t create trans " . $t->{‘id’} . “\n” .
Dumper($t);
close DEBUG;
#exit;
}

This error occurred on 1,478 tickets out of a total of 23,498.
Basically, the end result was that the ticket was imported, but
missing some history.

When I looked at a particular errored transaction, I could not find
a reason why it would have caused a problem:
Couldn’t create trans 140427
$VAR1 = {
‘OldValue’ => ‘10’,
‘Type’ => ‘Give’,
‘Field’ => ‘Owner’,
‘Ticket’ => ‘20718’,
‘Created’ => ‘2004-12-31 00:04:28’,
‘id’ => 140427,
‘NewValue’ => ‘1698’,
‘Creator’ => ‘1698’,
‘ActivateScrips’ => ‘0’
};

RT2 Database Entry:
mysql> select * from Transactions where Ticket=‘20718’;
| id | EffectiveTicket | Ticket | TimeTaken | Type | Field |
OldValue | NewValue | Data | Creator | Created |
| 130616 | NULL | 20718 | 0 | Create | NULL |
NULL | NULL | NULL | 5 | 2004-10-29 03:04:29 |
| 140426 | NULL | 20718 | 0 | Status | Status |
new | resolved | NULL | 5 | 2004-12-31 00:04:28 |
| 140427 | NULL | 20718 | 0 | Give | Owner |
2 | 5 | NULL | 5 | 2004-12-31 00:04:28 |
3 rows in set (0.00 sec)

RT3 Imported Version of the ticket:
mysql> select * from Transactions where ObjectId=‘20718’ AND
ObjectType=‘RT::Ticket’;
| id | ObjectType | ObjectId | TimeTaken | Type | Field |
OldValue | NewValue | ReferenceType | OldReference | NewReference |
Data | Creator | Created |
| 130616 | RT::Ticket | 20718 | 0 | Create | NULL | NULL
| NULL | NULL | NULL | NULL |
| 1698 | 2004-10-29 03:04:29 |
1 row in set (0.00 sec)