Rt2_to_rt3 only exports userid numbers no user details?

Hey Everyone,
I’m keeping my fingers crossed that someone out there can help me. I’ve
been through the Jan05/Feb05 archives and can’t find anything on this issue.

The closest threads are:
Dumpfile-to-rt3 > My problem isn’t ticket text going to rt3 it’s dumping
users from rt2 (or more specifically my problem with anything going to RT3
is because of the problems dumping users from rt2)
RT2 to RT3 user import problems > Someone doing their own hackery to import
and got no replies (not in Jan when he posted anyway)

Maybe I just didn’t find the right thread, so if my answer is already out
there please just point me in the right direction.

We have a 2.0.15 instance running, and a 3.4.0 installed. The dump script
from 2.0.15 does run and complete without errors however the import script
fails. Upon check the metadata file from the dump I see that the only user
information that was actually dumped was the numeric userids (see example
below). I think I’m using version 1.23 of the tool (the readme has the
following date at the bottom with your contact info: 24 Jan 2003). The
versions of the tool seem a little misleading/confusing based on copyright
dates etc there is a version 1.8 (or 1.9) in the devel downloads area but
it’s dated older (2003) then 1.23 (2004). Am I just using the wrong version
of the tool?

This is what the user section of metadata looks like (only with a lot more
entries :wink: ) :

‘User’ => [
{
‘id’ => ‘1112’
},
{
‘id’ => ‘819’
},
{
‘id’ => ‘301’
}
],

Any assistance would be greatly appreciated.

Thanks,
Rick

The two installations are completely separate. The lib and etc lines (as
applicable) point the appropriate places.

RickFrom: Drew Barnes [mailto:barnesaw@ucrwcu.rwc.uc.edu]
Sent: Friday, February 04, 2005 2:00 PM
To: Rick Mitchell
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt2_to_rt3 only exports userid numbers no user
details?

You need to dump the data before you install anything from the 3.x tree.
From the README:

Tell rt-2.0-to-dumpfile where your RT libraries live. (Edit the 'use
lib' lines)

Execute:
rt-2.0-to-dumpfile  DIRNAME

DIRNAME will now contain one file called "metadata" and one
subdirectories
which contain about 1000 files, 1 file per ticket.


Install rt3. Let it set up your rt3 database.

Tell dumpfile-to-rt-3.0 where your RT libraries live. (Edit the 'use
lib' lines)

Rick Mitchell wrote:

Hey Everyone,
I’m keeping my fingers crossed that someone out there can help me.
I’ve been through the Jan05/Feb05 archives and can’t find anything on this
issue.

The closest threads are:
Dumpfile-to-rt3 > My problem isn’t ticket text going to rt3 it’s
dumping users from rt2 (or more specifically my problem with anything
going to RT3 is because of the problems dumping users from rt2)
RT2 to RT3 user import problems > Someone doing their own hackery to
import and got no replies (not in Jan when he posted anyway)

Maybe I just didn’t find the right thread, so if my answer is already
out there please just point me in the right direction.

We have a 2.0.15 instance running, and a 3.4.0 installed. The dump
script from 2.0.15 does run and complete without errors however the
import script fails. Upon check the metadata file from the dump I see
that the only user information that was actually dumped was the numeric
userids (see example below). I think I’m using version 1.23 of the tool
(the readme has the following date at the bottom with your contact
info: 24 Jan 2003). The versions of the tool seem a little
misleading/confusing based on copyright dates etc there is a version
1.8 (or 1.9) in the devel downloads area but it’s dated older (2003)
then 1.23 (2004). Am I just using the wrong version of the tool?

This is what the user section of metadata looks like (only with a lot more
entries :wink: ) :

‘User’ => [
{
‘id’ => ‘1112’
},
{
‘id’ => ‘819’
},
{
‘id’ => ‘301’
}
],

Any assistance would be greatly appreciated.

Thanks,
Rick


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

RT Administrator and Developer training is coming to your town soon!
(Boston, San Francisco, Austin, Sydney) Contact training@bestpractical.com
for details.

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

You need to dump the data before you install anything from the 3.x tree.
From the README:

Tell rt-2.0-to-dumpfile where your RT libraries live. (Edit the 'use
lib' lines)

Execute:
rt-2.0-to-dumpfile  DIRNAME

DIRNAME will now contain one file called "metadata" and one
subdirectories
which contain about 1000 files, 1 file per ticket.


Install rt3. Let it set up your rt3 database.

Tell dumpfile-to-rt-3.0 where your RT libraries live. (Edit the 'use
lib' lines)

Rick Mitchell wrote:

|# Hey Everyone,
|# I’m keeping my fingers crossed that someone out there can help me. I’ve
|# been through the Jan05/Feb05 archives and can’t find anything on this issue.
|#
|# The closest threads are:
|# Dumpfile-to-rt3 > My problem isn’t ticket text going to rt3 it’s dumping
|# users from rt2 (or more specifically my problem with anything going to RT3
|# is because of the problems dumping users from rt2)
|# RT2 to RT3 user import problems > Someone doing their own hackery to import
|# and got no replies (not in Jan when he posted anyway)
|#

I too am going through this process currently and am also having the
same problem. Anyone have a hint/answer?

Doing a quick/simple debug of the code shows that in export_user…
my $blank_User = RT::User->new($RT::SystemUser);
$blank_User->_Accessible( ‘Foo’, ‘read’ );
my $acc = $blank_User->{_AccessibleCache};

$acc does not get set so $param in the following…

foreach my $param ( sort keys %$acc, 'id' ) {

gets nothing but ‘id’

            Tim Rosmus <trosmus@nwnexus.net>
               Postmaster / USENET / DNS
                  Northwest Nexus Inc.

If you have 3.x installed on the same machine as 2.x, it will parts of
the 3.x install and dump bad data. Hence the instruction to dump from
2.x BEFORE installing 3.x

Telling them to use different libs does not matter, speaking from
experience.

Rick Mitchell wrote:

[mailto:rt-users-bounces@lists.bestpractical.com]On Behalf Of Rick
MitchellSent: Friday, February 04, 2005 12:46 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] rt2_to_rt3 only exports userid numbers no user
details?

This is what the user section of metadata looks like (only with a lot more
entries :wink: ) :

‘User’ => [
{
‘id’ => ‘1112’
},
{
‘id’ => ‘819’
},
{
‘id’ => ‘301’
}
],

|# If you have 3.x installed on the same machine as 2.x, it will parts of the
|# 3.x install and dump bad data. Hence the instruction to dump from 2.x BEFORE
|# installing 3.x
|# Telling them to use different libs does not matter, speaking from experience.
|#

My setup is on two completely different machines and I am having the same
problems Rick is. V3 is no where near V2 during the dump.

|# Rick Mitchell wrote:
|#
|# > The two installations are completely separate. The lib and etc lines (as
|# > applicable) point the appropriate places.
|# >
Tim Rosmus trosmus@nwnexus.net
Postmaster / USENET / DNS
Northwest Nexus Inc.

Rick Mitchell wrote:

This is what the user section of metadata looks like (only with a lot more
entries :wink: ) :

‘User’ => [
{
‘id’ => ‘1112’
},

I had a similar problem. In my case the problem was a version conflict,
in what I think was the SearchBuilder perl file (my perl knowledge is
like 0). I solved it by taking an older version of perl libraries (5.005
IIRC).

Version Info as requested:

Solaris 8
RT 2.0.15 (and 3.4.0)
Perl 5.8.0
Storable 2.13
MySQL 4.0.23

If you have 3.x installed on the same machine as 2.x, it will parts of
the 3.x install and dump bad data. Hence the instruction to dump from
2.x BEFORE installing 3.x

Telling them to use different libs does not matter, speaking from
experience.

Part of the problem is that the libs from RT2 are incompatible with some
of the newer versions of DBIx::SearchBuilder. In particular, the
AccessibleCache stuff has been seriously reworked/removed so the export
script’s attempts to access the data this way don’t return anything.

In order to export properly from RT2 I had to downgrade the Perl
installation to using an ancient SearchBuilder, something like 0.48 in
my case (I was exporting from RT 2.0.7). I ended up building a custom
Perl just to do the export, with all the old RT2 Perl dependencies in
there.

  • Julian

– Julian C. Dunn, B.A.Sc, P.Eng. Julian_Dunn@cbc.ca
– Platform Administrator, CBC.ca Production & Operations
– Office: 2C310-Q * Tel.: (416) 205-3311 x5592

Part of the problem is that the libs from RT2 are incompatible with some
of the newer versions of DBIx::SearchBuilder. In particular, the
AccessibleCache stuff has been seriously reworked/removed so the export
script’s attempts to access the data this way don’t return anything.

While this was true in the SearchBuilder 1.0.x series, I’ve been happily
running RT2 instances against DBIx::SearchBuilder 1.1x and 1.2x

Part of the problem is that the libs from RT2 are incompatible with some
of the newer versions of DBIx::SearchBuilder. In particular, the
AccessibleCache stuff has been seriously reworked/removed so the export
script’s attempts to access the data this way don’t return anything.

While this was true in the SearchBuilder 1.0.x series, I’ve been happily
running RT2 instances against DBIx::SearchBuilder 1.1x and 1.2x

What I meant is that the export RT2 script (rt2-to-dumpfile) doesn’t
work well against newer SearchBuilders because it appears to poke around
in internal data structures like AccessibleCache that have gone away.

  • Julian

– Julian C. Dunn, B.A.Sc, P.Eng. Julian_Dunn@cbc.ca
– Platform Administrator, CBC.ca Production & Operations
– Office: 2C310-Q * Tel.: (416) 205-3311 x5592

Ya that was part of it, downgrading DBIx::SearchBuilder made the export
work. I’ve once again upgraded it however the import to 3.4.0 is now failing
with syslog issues.

Rick

[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Johan JonkersSent: Friday, February 04, 2005 2:39 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] rt2_to_rt3 only exports userid numbers no user
details?

Rick Mitchell wrote:

This is what the user section of metadata looks like (only with a lot more
entries :wink: ) :

‘User’ => [
{
‘id’ => ‘1112’
},

I had a similar problem. In my case the problem was a version conflict, in
what I think was the SearchBuilder perl file (my perl knowledge is like 0).
I solved it by taking an older version of perl libraries (5.005 IIRC).

http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

RT Administrator and Developer training is coming to your town soon!
(Boston, San Francisco, Austin, Sydney) Contact training@bestpractical.com
for details.

Be sure to check out the RT Wiki at http://wiki.bestpractical.com