Hello, PROBLEM: import-1.0-to-2.0.pl does not keep correct dates and requestors (e.g. date_created ) WANTED: patch for import-1.0-to-2.0.pl or rt-2-0-0
I tested an upgrade of an rt-1.0.1 system with about 50.000 tickets to rt-3.0.12 and upgrade to rt-3.4.5. It basically worked by using import-1.0-to-2.0.pl to convert to rt-2-0-0 and then convert with the rt2-to-rt3-1.23 scripts to latest 3.0.x version (rt-3.0.12). But after migrating "successfully" I noticed that e.g. the "Created" entries for "Ticket" and "Transactions" tables do contain time stamps of the time frame when the import-1.0-to-2.0.pl was running and not the original creation date of the tickets and transactions as expected. I found out, that already import-1.0-to-2.0.pl puts these wrong dates into rt2 I added some "print" commands to import-1.0-to-2.0.pl and e.g. "date_created" in epoche seconds is correctly read from rt1 and also correctly transformed to the "2006-07-04 13:05:02" format but just not written into rt2 database. This makes it hard to find old tickets and impossible to run statistic tools. I am not sure if this is a problem of rt-2-0-0 or import-1.0-to-2.0.pl but I found this related thread: http://www.gossamer-threads.com/lists/rt/users/11205 > i think that is what i used back when i converted. when i did it, it > did not carry over the requestor or ticket creation and resolution > dates (ie- sets all requestors to whatever you are when you import, > and dates to current date). i hacked like four lines to carry these > over and mailed it to the list, you can check the archives if > interested. fyi and good luck! That sounds that this is a known problem and that there is a patch around?! * Has somebody please this patch available for me or another solution ? I am using this version for import-1.0-to-2.0 from http://download.bestpractical.com/pub//rt/contrib/2.0/rt-addons/import-1.0-to-2.0 rt-addons/import-1.0-to-2.0,v 1.6 2002/01/25 20:14:55 jesse Exp $ * Should I first update rt-1.0.1 to rt-1.0.7 before migrating to rt-2.x ? * Should I use latest rt2 (rt-2-0-15) insead of earliest rt2 (rt-2-0-0 ) during import-1.0-to-2.0 migration ? PLEASE HELP ME ! best regards, Jodok BTW: dumpfile-to-rt-3.0 failed if using DBIx-SearchBuilder-1.26 while running rt-2.0-to-dumpfile but I was able to run these scripts rt2-to-rt3-1.23 fine with DBIx-SearchBuilder-1.01. rt1 mysql> select id,trans_date from transactions LIMIT 3; +-----+------------+ | id | trans_date | +-----+------------+ | 81 | 967200331 | | 80 | 967200325 | | 115 | 967214097 | +-----+------------+ rt1 mysql> select serial_num,date_created from each_req LIMIT 3; +------------+--------------+ | serial_num | date_created | +------------+--------------+ | 1 | 966001877 | | 2 | 966422061 | | 3 | 966425398 | +------------+--------------+ rt2 mysql> select id,Created from Transactions LIMIT 3; +----+---------------------+ | id | Created | +----+---------------------+ | 1 | 2006-07-04 15:03:43 | | 2 | 2006-07-04 15:03:43 | | 3 | 2006-07-04 15:03:43 | +----+---------------------+ rt2 mysql> select id,Created from Tickets LIMIT 3; +----+---------------------+ | id | Created | +----+---------------------+ | 1 | 2006-07-04 15:03:43 | | 2 | 2006-07-04 15:03:43 | | 3 | 2006-07-04 15:03:43 | +----+---------------------+ -- Jodok Ole Muellers | Verizon Business Internet Software System Engineer | Sebrathweg 20 EMEA Server & Service Management | D-44149 Dortmund, Germany phone: +49 (0)231 972 1432 | vnet : 317 1432 mail : [EMAIL PROTECTED] | fax : +49 231 972 2587 pgp : gpg --keyserver blackhole.pca.dfn.de --recv-keys 5A2A106E _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html
