Dumpfile-to-rt3

Hello again.

I’m going around in circles again.

I’m still trying to move our rt2.0.13 from an older system to rt3.4.0 on
a new system.

The new system is a dual processor Dell 1850 with 1GB ram and 73GB of
SCSI disk, RAID 1. Other specifics:

  • Fedora Core 3, all updates applied
  • Apache 2.0.52
  • MySQL 4.1.9
  • Perl 5.8.5
  • DBD::mysql 2.9004
  • DBIx::SearchBuilder 1.22
  • Storable 2.13

I’ve dumped out the rt-2 data using version 1.23 of the rt2-to-rt3
utility. When I try to import the data back into any flavor of rt from
3.0.12 to 3.2.2 through 3.4.0 I get these errors on every ticket:

File is not a perl storable at …/…/lib/Storable.pm (autosplit into
…/…/lib/auto/Storable/_retrieve.al) line 328, at dumpfile-to-rt-3.0
line 496

I get some stuff across, but ticket text is missing.

Anyone have any ideas?

Thanks,
Gary

Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.aspx

The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.

Hello again.

I’m going around in circles again.

I’m still trying to move our rt2.0.13 from an older system to rt3.4.0 on
a new system.

Try an import into RT 3.2 and upgrade from there?

I’m still trying to move our rt2.0.13 from an older system to rt3.4.0 on
a new system.

Try an import into RT 3.2 and upgrade from there?

This once again revives the need for an any->any export/import. Is it
possible to define a canonical XML schema for user and ticket data
that could hold any version’s contents? Then it would be a matter
of using perl sql<->xml modules to do the grunge work of conversions
between RT versions and underlying database changes.

Les Mikesell
les@futuresource.com

Hello again.

I’m going around in circles again.

I’m still trying to move our rt2.0.13 from an older system
to rt3.4.0 on
a new system.

Try an import into RT 3.2 and upgrade from there?

Like my original message said, I’ve tried various flavors including
3.0.12, 3.2.2 and 3.4.

I’ll try some more, but I think the issue is unrelated to the rt
version.

Gary

Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.aspx

The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.