risk of migrating from sql to oracle in CLM 2012
One answer
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.
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.