It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,883
×7,479
×5,944
×3,951
×2,352
×1

question asked: Dec 21 '17, 3:58 p.m.
question was seen: 2,054 times
last updated: Jan 04 '18, 1:33 p.m.

Related questions

Migration by import from RTC 4.x to 6.0.4 instead of upgrading (2 paasses)?

1
long TRUONG (365●4●123●147) | asked Dec 21 '17, 3:58 p.m.
edited Dec 21 '17, 7:33 p.m. by Muralidhar Rajagopal (101●1●4)

 Is it a sound strategy to install a brand new instance of RTC  (CLM)  6.0.4 with brand new DBs, then migrate data, via imports, from 4.x projects, to avoid a 2-steps upgrade ?


Would it save time, efforts, headaches over upgrading in two stages 4.x ==> 5.x ==> 6,x?
Pros and Cons of each vs the other?

Comments
Liora Milbaum commented Dec 25 '17, 7:06 a.m.

 A upgrade wrapper which executes the 2-steps upgrade might be useful.

Accepted answer

0
permanent link
Donald Nong (14.5k●6●14) | answered Dec 21 '17, 7:40 p.m.

During the upgrade, metadata (data structure) needs to be changed as well. The data that you export from a 4.0.x instance is not compatible with newer versions, so the proposed import part will not succeed.

long TRUONG selected this answer as the correct answer
Comments
long TRUONG commented Dec 23 '17, 12:49 p.m.

 Thx Don,


Could you elaborate and also speculate on possible success on a limited subset of what to import into RTC:
  • What if we only import WI and a chosen snapshot of the versioned code?
  • To me even just import the WI's :
    • Import the process template for each project area? Are there meta data that would fail this import?
    • Import the user base, don't remember if there is a current process for this, or we have to recreate it manually.
BTW Has there ever been any extraordinaire circumstances that an IBM customer has chosen to go this route? or has been recommended or supported by IBM on such solution?

Geoffrey Clemm commented Dec 24 '17, 8:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

The only time I'm aware of IBM recommending the use of export/import is to "copy" a project area from one repository to another existing repository.   The likelihood of at least some of your users wanting access to the data that is not brought over by export/import is sufficiently high that it is unlikely that IBM would ever recommend this as a way to shortcut a double upgrade.

long TRUONG commented Jan 04 '18, 1:33 p.m.

Thx Geoffrey,


Nice to hear someone corroborating with one's own thoughts.

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.