It's all about the answers!

Ask a question

Upgrade RTC from 2.0.0.2 to 3M5


David Csikkel (1313516) | asked Apr 21 '10, 11:07 a.m.
Hello,

I couldn't find guideline for upgrading from RTC 2.0.0.2 to 3M5?!?
Is it necessary to export data from 2.0.0.2 and import to newly created tables in 3M5 via repotools?
Or is it enough to only somehow update DB structure/model?


Thank you in advance

David Csikkel
Tieto, Consultant

3 answers



permanent link
Sreedhar Rella (24178) | answered Apr 21 '10, 3:49 p.m.
JAZZ DEVELOPER
Hello David,

FYI: There is a good article on who should upgrade to what releases (https://jazz.net/wiki/bin/view/Main/MigrationRTC20).

If you a regular Customer you should hold until 3.0 GA, and if you are an early adopter then wait until 3.0 Beta 1. Otherwise please review the release notes at
https://jazz.net/downloads/rational-team-concert/milestones/3.0M4?p=releasenotes

and

https://jazz.net/downloads/rational-team-concert/milestones/3.0M5?p=releasenotes

permanent link
Adrian Cho (82113322) | answered Apr 21 '10, 11:11 p.m.
JAZZ DEVELOPER
David

There is no more repository migration. What Sreedhar is saying is that generally we do not support going from say a previous release to some random milestone in the next development cycle. That said, the 3.0 development cycle is weird and the first milestone we published was M4 and the dev team went straight from self-hosting on 2.0.0.2 to 3.0 M4. So you can do that and then safely go to M5. All you will need to do is follow the instructions in the release notes that specify things like addTables. Although it's not as repository model changes, it is still a modification to your database schema so we still recommend doing a database backup before you do the addTables, etc.

Hope that helps.

Adrian

permanent link
Adrian Cho (82113322) | answered Apr 21 '10, 11:15 p.m.
JAZZ DEVELOPER
David

I should add, that as you will see on top of the web page of any early milestone builds, we don't recommend using them in production. We do appreciate that you want to check it out and we look forward to any feedback but it's best to kick the tires on it and not upgrade your 2.0.0.2 production. Note also that we discovered a memory leak in the M5 build engine and have released an M5a update for this.

Cheers

Adrian

Your answer


Register or to post 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.