It's all about the answers!

Ask a question

risk of migrating from sql to oracle in CLM 2012

Natalia Trofimov (391714) | asked Mar 01 '13, 1:20 p.m.
edited Mar 04 '13, 1:46 p.m. by Joseph Pesot (61)
We are planning to migrated the data from MS SQL db to Oracle db. I heard there is a risk involved in migrating the data from one db vendor to another. did anybody done it successfully or anybody had problems? thk, Natalia

One answer

permanent link
Tory Jaskoviak (52015) | answered Mar 05 '13, 2:45 p.m.
Hi Natalia,

RQM supports database migration from one db vendor to another using repotools -export and -import. I'm not sure what version of RQM you are using but here is a link to instructions on migration: RQM 3.0, RQM 4.0.
Although the instructions are migrating from Derby, its the same process for any db.

It sounds like you are keeping the same RQM instance. If this is the case then you should no other problems.

However, if you are trying to migrate to a different RQM instance also, you will run into issues with the public URI. Every artifact in the database has a reference to the public URI of the original RQM instance. The solution would be to upgrade to RQM 4.0 so that you can perform a server rename, which changes the references of all database artifacts to point to the new RQM instance instead.

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.