Steps to follow to migrate from RTC 30 M8 to RTC 30 GA
Hi all,
what would be the best path for migrating from RTC 30 M8 to RTC 30 GA? Do we have to use the repotool to export and import the data for each one of the releases (RC0, RC1, RC2, RC3) before being able to migrate to the Released 30 Version? We did try to migrate from M8 to RC3 but the migration failed. We did run repostool-jts.sh -addTables and repotool-ccm.sh -addTables prior of starting the RC3 Jazz Server, but it seems that many items seemed to be missing during the repotool-ccm.sh -import.. When the server was started, we were not able to open Iteration plans, and for WI, we can only list them but once we try to open them it complains about missing artifacts. Please advise for the good migration path from a earlier build of RTC 30. Thanks all! |
7 answers
Hi all,
Is there a specific migration path such as RTC 30 M8 > RTC30 RC0 and > RTC GA? Please advise. |
Officially, no. We only ever support milestone to milestone and release to milestone or beta to milestone. However I believe that in theory it should be fine since by that point we were split into JTS and CCM. However I cannot say that we have tested this particular path. You should just have to do addTables for both repositories. Please ensure that you backup your repositories (you should always do this before doing any addTables any other repository migration) first.
|
Hello Adil,
As Adrian underlined, this not a supported scenario. And we can not guarantee that your migrated repos DB's will not have a hidden problem. The repos Online verify tool https://jazz.net/wiki/bin/view/Main/OnlineVerifyTool might help though. -- Eric JODET Jazz Development - L3 Maintenance |
Hi all,
I've uziped the Verification tools under JAZZ_SERVER_HOME/server and ran sudo ./repotools-jts.sh -clean But it failed giving that error. Repo Tools Provisioning using "./conf/jts/provision_profiles". CRJAZ0281I The dependency bundle "com.ibm.team.repository.service" is not installed and no features available for installation provided that bundle. CRJAZ0288I Failed to install the profile feature "com.ibm.team.repository.service.verifier.systemtable.feature" from the update site "file:jts/sites/verifier-update-site" referenced in the profile file "./conf/jts/provision_profiles/verify-profile.ini". CRJAZ1834E Error provisioning the server. Di I miss a specific step? Thanks a lot for your time! Hello Adil, |
Officially, no. We only ever support milestone to milestone and release to milestone or beta to milestone. However I believe that in theory it should be fine since by that point we were split into JTS and CCM. However I cannot say that we have tested this particular path. You should just have to do addTables for both repositories. Please ensure that you backup your repositories (you should always do this before doing any addTables any other repository migration) first. Hello Adrian, but how about the jazz.net site? It was running on a specific Milestone and was migrated step by step until reaching the GA right? Please advise. |
Hello Adil,
may you please tell us about the location from which you downloaded the verification tool? What are the plug-in versions included with the zip file? Thanks. Eric. -- Eric JODET Jazz Development - L3 Maintenance Le 11/26/2010 4:38 PM, Thunder a crit : Hi all, |
Geoffrey Clemm (30.1k●3●30●35)
| answered Nov 26 '10, 1:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I would have phrased it somewhat differently:
- There are three levels of builds: milestones, betas, and releases. - Every beta is a milestone, and every release is a beta (logically). - You can always upgrade from a build at one level directly to the next build at that same level (so you can upgrade from a milestone to the next milestone, from a beta to the next beta, and from a release to the next release). So the shortest way to upgrade from any given milestone to any given subsequent release is: - Upgrade from that milestone to the next milestone until you reach a milestone that is a beta (0 or more upgrades) - Upgrade from that beta to the next beta until you reach a beta that is a release (0 or more upgrades) - Upgrade from that release to the next release until you reach the release that you want. Cheers, Geoff On 11/25/2010 11:23 PM, acho wrote: Officially, no. We only ever support milestone to milestone and |
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.