Rt-2.0-to-dumpfile errors

When running rt-2.0-to-dumpfile, I get a similar error on every record:

Exporting ticket 623DBD::Pg::st execute failed: ERROR: column “requestors” does not exist at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Handle.pm line 410.
RT::Handle=HASH(0x80f806c) couldn’t execute the query ‘SELECT requestors FROM Tickets WHERE id = ?’ at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Handle.pm line 417.
Can’t locate object method “fetchrow_array” via package “Class::ReturnValue” (perhaps you forgot to load “Class::ReturnValue”?) at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Record.pm line 574.

Any ideas? I’m not about to try importing the files I got.

When I ran into similar problems a month ago, they said it was cause
I had not enlargened max_allowed_packet in my.cnf .

But after making that several orders of magnitude larger than the largest
attachment in RT2, and starting over with the script, things still broke
on the exact ticket attachment, with the exact error message.

It fails really inelegantly too. Instead of just iterating over the failed
attachment and going on, so the admin might be left with a working migration
minus a couple of attachments, the script stops running at the error,
which makes migration impossible even if one attachment fails.

At some point consensus might form that even if the admin increases
max_allowed_packet, a migration still can fail, and diagnosis might
pick up from there. I gave up on migrating and started with a new RT3.

When running rt-2.0-to-dumpfile, I get a similar error on every record:

Exporting ticket 623DBD::Pg::st execute failed: ERROR: column “requestors” does not exist at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Handle.pm line 410.
RT::Handle=HASH(0x80f806c) couldn’t execute the query ‘SELECT requestors FROM Tickets WHERE id = ?’ at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Handle.pm line 417.
Can’t locate object method “fetchrow_array” via package “Class::ReturnValue” (perhaps you forgot to load “Class::ReturnValue”?) at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Record.pm line 574.

Any ideas? I’m not about to try importing the files I got.


The rt-users Archives

RT Developer and Administrator training is coming to LA, DC and Frankfurt this spring and summer.
http://bestpractical.com/services/training.html

Sign up early, as class space is limited.

Dave Dennis wrote:

When I ran into similar problems a month ago, they said it was cause
I had not enlargened max_allowed_packet in my.cnf .

Actually, your problem was completely different, involving the
3.0 import, not the 2.0 export.

It fails really inelegantly too. Instead of just iterating over the failed
attachment and going on, so the admin might be left with a working migration
minus a couple of attachments, the script stops running at the error,
which makes migration impossible even if one attachment fails.

The failed attachment is a sign of deeper damage. Not fixing that
is likely to bite you in other ways, too.

There are at least two problems I can think of that cause attachment
creation to fail:

  1. max_allowed_packet being too small
  2. old version of perl with character encoding bugs

either of those will cause pain if not addressed, regardless of how
attachments are handled at import. When would you rather disover
the damage – at import, or 6 months down the track?

Michael R. Wayne wrote:

RT::Handle=HASH(0x80f806c) couldn’t execute the query ‘SELECT requestors FROM Tickets WHERE id = ?’ at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Handle.pm line 417.
Can’t locate object method “fetchrow_array” via package “Class::ReturnValue” (perhaps you forgot to load “Class::ReturnValue”?) at /usr/local/lib/perl5/site_perl/5.6.1/DBIx/SearchBuilder/Record.pm line 574.

That’s interesting. What versions of RT, rt2-to-rt3, and
Class::ReturnValue do you have?