It's all about the answers!

Ask a question

Registering a RTC to a different JTS after old JTS is not recoverable

Bogdan Dragoiu (611) | asked Jun 18 '14, 3:58 a.m.

our 4.0.6 environment recently hard crashed during a backup operation. Consequently the JTS database was not recoverable.

What I have tried to do so far is set up a new JTS+RTC environment using the same public URI and have used the repotools import for the JAZZ database. This shows some promise as I mainly get this error:

CRJAZ2488E The friend entry for the Jazz Team Server contains a consumer key that is invalid (it is not being accepted by the Jazz Team Server).
I get a bunch of other errors, but I think the root cause is the one above. Examples of other errors are:

The "" service failed to activate because a service that it depends on, "", failed to be activated.ID CRJAZ1972E
As a disclaimer, we at this point want our Work Items back, we do not care for the Dashboards and other user customization.
Other things I have tried so far:
- the same procedure as describe above but using a different public URI (not a good idea in hindsight)
- registering the old still working /jazz to a new remove JTS, but this throws the error that the jazz server is already registered with a different JTS
- tried making and breaking a lot of friendships between servers

A few of the people I have already talked to who are also top contributors to jazz and this website seem to have the same idea that a database change might solve it. Does anyone know how to change the consumer key of a jazz database to a new jts server?

I've had a look in the database and have found the FRIEND.FRIENDS table which seems promising and the REPOSITORY.OAUTH_CONSUMER_REGISTRATION table. However I can't seem to find the relation between these tables.

One answer

permanent link
Krzysztof Ka┼║mierczyk (7.4k370102) | answered Jun 18 '14, 4:41 a.m.
Hi Bogdan,
It will  be sad what I say to you but there is no option to use RTC with another JTS. You must start using your new CLM solution from scratch and remember about regular back ups in the future.

Alternatively you can try contacting consulting services to ask  for moving your database (if it is technically possible).

Bogdan Dragoiu commented Jun 18 '14, 9:39 a.m.

Then how about de-registering the RTC server that has lost it's JTS and then re-registering it somewhere else? Could that be an option?

Your answer

Register or to post your answer.