repotools hanging on migration from m6a to RC2
I'm trying to get one of my jazz servers caught up to the latest release. Currently I'm trying to migrate my repository from m6a to RC2 and it appears to be hanging (log below). This is a DB2 9.1 FP4a database.
[root@jazzdev server]# ./repotools.sh -import fromFile=/usr/data/backups/jazzrepo_for_m6a.tar teamserver.properties=/usr/data/backups/teamserver_2008-05-29.properties |
5 answers
On Fri, 30 May 2008 19:07:56 +0000, parrym wrote:
I'm trying to get one of my jazz servers caught up to the latest How big is /usr/data/backups/jazzrepo_for_m6a.tar and how long has it been hung there? - Dmitry |
export_from_M6a.tar is 48MB in size. My first attempt to import that started yesterday around 2pm and I let it run overnight. When I came in this morning it was still at that same message. I killed that process and re-started it assuming it had hung. Looks like this attempt has been running about an hour and forty minutes....
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND |
Well I got sick over the weekend so this latest attempt has been running since Friday and still sitting at "Importing 'ChangeEvent' items."
Not sure if this is relevant or not but the Jazz database was created with the following db2 command on db2 9.1.. db2 create database jazz on /usr/data/databases/jazz using codeset UTF-8 territory US |
This appears to be a user error. As mentioned previously I was trying to migrate across numerous releases and inadvertently was passing the export from m5a into the RC2 import as opposed to the m6a export.
|
Just closing the loop here. I was able to migrate successfully from M5a -> M6a -> RC2 -> RC3 -> RC4 with no further complications.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.