It's all about the answers!

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

×7,450
×4,711

question asked: Jun 06 '18, 8:25 a.m.
question was seen: 1,097 times
last updated: Jun 07 '18, 10:09 a.m.

Related questions

How long does it take to upgrade from CLM 6.0.2 to 6.0.5?

0
Amie Norgrove (13●3) | asked Jun 06 '18, 8:25 a.m.

I know the answer will vary from company to company, but I'm looking for a ballpark answer here -- days, weeks, etc. We're being told that it will take two weeks, with our engineers completely unable to use the tools during that time.  That seems excessive to me. I'm not sure how any company could afford to use the tools if that was the typical case every time you upgrade versions.

Accepted answer

1
permanent link
Ralph Schoon (63.4k●3●36●46) | answered Jun 07 '18, 10:09 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

It is also worth mentioning that it is not always necessary to upgrade all at once.
JTS can usually be upgraded before the other applications. In the past it was possible to upgrade the applications later.

Most customers I am aware of upgrade over a weekend. If the database is huge it might take more time - I agree it would be best to do a test migration - we always suggest this.

2 weeks does not sound right. I know that migrating between database vendors can take a long time due to repotools export/import performance, but this is usually not the scenario customers perform.

Amie Norgrove selected this answer as the correct answer

2 other answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Luca Martinucci (1.0k●3●97●112) | answered Jun 06 '18, 10:35 a.m.
edited Jun 06 '18, 10:36 a.m.

As you said, the duration depends on the CLM environment, namely the amount of data stored in the databases.

Anyway, have you considered running an online migration to reduce the downtime?
The duration of the online migration can be estimated using the onlineMigrateEstimate command: https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Fr_repotools_onlineMigrateEstimate.html

0
permanent link
Alick Banda (43●7●18) | answered Jun 07 '18, 9:59 a.m.

 Hi Amie,


Telling you how long the upgrade will take is almost impossible, but I would recommend the following:
1. If you do not have one, plan, and create a staging environment on CLM 6.0.2
2. Using the staging environment, try to upgrade your environment to your desired version. This will not only give you an idea of how long the upgrade will take, but also the complexity and the effort of the upgrade (testing rollbacks etc.). 
3. Once upgrade is successfully done on a staging environment, you can then plan for your upgrade (plan the downtime, plan resources, log your support calls just in case something goes wrong etc.)
4. Perform the upgrade.

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.