What causes the RTC6.0 db lock issue during installs?
Following is our configuration for a sandbox environment using the evaluation topology:
Database: DB2 10.5
Container: Websphere App Server, Stand-alone, 8.5.7
Operating system: RHEL Linux 7.1
Product: RTC 6.0
We have had multiple problems installing the RTC product, using the interactive installation guide.
1) CCM installation step via the installation manager initially showed success. However, JAZZ_HOME/server/conf/ccm & the ccm.war file did not get generated, and subsequently, CCM registration with JTS failed.
2) Re-installation of CCM via installation manager did create the missing files. However, the re-installation caused the CRJAZ1770E error: The configured database lock id does not match the lock id in the database.
3) To resolve this, we had to manually update the teamserver.property files to point to DB2 (they were somehow configured by default for derby), even after we had configured DB2 during JTS setup.
4) Even then repotools.sh -resetRepoLockId does not work. We end up re-creating the JTS & CCM databases.
5) After this, JTS setup is successful, but CCM setup again errors out during table creation with the db lock issue.
Please advise the best course of action to resolve this.
Accepted answer
You have to install separate DB's for all the applications that need one. I suspect you are trying to access one DB with all applications or you mistyped the DB connection for one, using the DB of another application.
I would recreate all the DB's and make sure to configure the correct one per application. Otherwise, there is a repotools command to remove the lock.
Comments
Hi Ralph,
Many thanks for the prompt help. Our data sources on the container were pointing to the same database. This now works correctly, thanks to your advice.
I have a follow-up question: The setup process during installation also sets up data-sources for CLM & JTS datawarehouses, in addition to the DCC setup. Is it necessary to use separate data-sources for each, or should we use the DCC database to store all reporting tables?
Hi Ralph,
Many thanks for the prompt help. Our data sources on the container were pointing to the same database. This now works correctly, thanks to your advice.
I have a follow-up question: The setup process during installation also sets up data-sources for CLM & JTS datawarehouses, in addition to the DCC setup. Is it necessary to use separate data-sources for each, or should we use the DCC database to store all reporting tables?
The Datawarehouse has its own database and indexes, that you set up, however, the appliactions point to the data warehouse. there is no separate datawarehous DB for each application. You set up a technical user to be able to talk to the DCC and JRS application.