It's all about the answers!

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

×10,958
×7,479
×4,712
×2,352
×267

question asked: Feb 14 '17, 11:46 a.m.
question was seen: 2,634 times
last updated: Feb 14 '17, 3:23 p.m.

Related questions

Migrating data to clean install

0
Adam Nicholson (38●4) | asked Feb 14 '17, 11:46 a.m.

Hi,

We are upgrading CLM from v3.0.1.3 to v4.0.7 for a project catching up. This is running with DB2 databases.

Would it be possible to back up the data of the v3 project areas, primarily RQM, and apply this to a clean v4 install?

Thanks in advance.

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Kevin Ramer (4.5k●9●186●201) | answered Feb 14 '17, 12:47 p.m.
edited Feb 14 '17, 3:23 p.m.

Doesn't the upgrade step(s) from v3 to v4 satisfy your requirements ?

There are no carving out/injection of project areas from either the back-end database or the repository itself.  It is all or none to be upgraded.   And aside from the database, an upgrade should always be done into a "clean install" i.e. a freshly installed CLM package including the needed JTS and/or applications.

There are also dependencies amongst JTS and its applications that must be met.  JTS must be "highest" ( at most 1 major version above its registered applications ) and if applications are co-located in the same J2EE provider ( i.e. installed in same WebSphere or Tomcat ) they must all be upgraded in the same "session".

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.