Does anyone have any suggestions for finishing this import? I’ve tried
going back and importing my incremental dumps and they are bombing out.
When I did the original import it was at 3.2.2 and then upgraded to
3.4.1 where I finished setting it up. Now doing the incremental on
3.4.1 produces the following errors in syslog:
Mar 16 08:23:25 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘disabled’ in ‘field list’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:25 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query ‘SELECT disabled FROM Users WHERE id = ?’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:25 ul174.principal.com RT: Can’t locate object method “fetchrow_array” via package “Class::ReturnValue” at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Record.pm line 624. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:25 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘Disabled’ in ‘field list’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:25 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query 'UPDATE Users SET Disabled=? WHERE id=? ’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:26 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘disabled’ in ‘field list’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:26 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query ‘SELECT disabled FROM Users WHERE id = ?’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:26 ul174.principal.com RT: Can’t locate object method “fetchrow_array” via package “Class::ReturnValue” at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Record.pm line 624. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:26 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘Disabled’ in ‘field list’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:26 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query 'UPDATE Users SET Disabled=? WHERE id=? ’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:26 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘disabled’ in ‘field list’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:26 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query ‘SELECT disabled FROM Users WHERE id = ?’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:26 ul174.principal.com RT: Can’t locate object method “fetchrow_array” via package “Class::ReturnValue” at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Record.pm line 624. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:27 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘Disabled’ in ‘field list’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:27 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query 'UPDATE Users SET Disabled=? WHERE id=? ’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:27 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘Ticket’ in ‘where clause’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:27 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query ‘DELETE FROM CustomFieldValues WHERE Ticket = ‘3101’’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:29 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘Ticket’ in ‘where clause’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:29 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query ‘DELETE FROM CustomFieldValues WHERE Ticket = ‘4005’’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:31 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘Ticket’ in ‘where clause’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:31 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query ‘DELETE FROM CustomFieldValues WHERE Ticket = ‘4006’’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:33 ul174.principal.com RT: DBD::mysql::st execute failed: Unknown column ‘Ticket’ in ‘where clause’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:33 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query ‘DELETE FROM CustomFieldValues WHERE Ticket = ‘5442’’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:34 ul174.principal.com RT: DBD::mysql::st execute failed: Duplicate entry ‘57829’ for key 1 at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 480. (/rt/rt3.4/lib/RT.pm:277)
Mar 16 08:23:34 ul174.principal.com RT: RT::Handle=HASH(0xab575f8) couldn’t execute the query ‘INSERT INTO Transactions (OldReference, Field, Type, id, OldValue, NewReference, NewValue, Creator, ObjectId, ReferenceType, Created, Data, ObjectType) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)’ at /usr/local/perl/lib/site_perl/5.8.6/DBIx/SearchBuilder/Handle.pm line 494. (/rt/rt3.4/lib/RT.pm:277)
From the command line:
[root@ul174 rt2-to-rt3-1.23]# ./dumpfile-to-rt-3.0 /rt/rt2dump2/dump2
Importing tickets…t-3101
.t-4005
.t-4006
.t-5442
Couldn’t create trans 57829
$VAR1 = {
‘Type’ => ‘Correspond’,
‘Ticket’ => ‘5442’,
‘Created’ => ‘2005-02-04 16:54:32+00’,
‘id’ => 57829,
‘Data’ => 'RE: [midrange.principal.com #5442] Correspondence: Password
',
‘Creator’ => ‘628’,
‘ActivateScrips’ => ‘0’
};
I’m assuming this has to do with the schema updates made between 3.2 and 3.4. How can I move forward without having to dump everything and start over at 3.2 with a drop db?
Matt-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com]On Behalf Of Millard,
Matt
Sent: Wednesday, March 09, 2005 12:21 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Finishing migration from rt2 to rt3
I’m finally comfortable with my rt3 installation and will soon be making
the cut over to the new system. If I do a make dropdb I loose all of my
configuration work correct? How can I go about dropping the users and
tickets, but keeping the configuration in place? I’ve got 9000 tickets
and several hundred users to drop and then reload on the new system. If
I import my ticktes using dumpfile-to-rt3 how does it handle tickets
that are dumplicated? I loaded all of our tickets a month ago and have
since created some test tickets to make sure everything was functioning.
These test tickets will conflict with real tickets in the new dump of
the tickets. Any suggestions?
Matt
-----Original Message-----
-----Message Disclaimer-----
This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect@principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.
Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act (“E-Sign”)
unless a specific statement to the contrary is included in this message.