The configured database lock id does not match

Hi Lisa,

the database and the teamserver.properties contain a lock ID for each database. This is to prevent users to accidentally connect to the wrong database.

I am not sure about your scenario, especially since you mention Derby and Oracle.

To migrate to a different database vendor you can use repotools -export and repotools -import. You can use backup/restore mechanisms if you stay with the same provider and architecture. See the help of your provider for backup and restore. See https://jazz.net/library/article/795 for general information on backup and restore. This article also contains a hint for Online backup for Oracle.

If you migrated or restored your database sucessfully and you are sure you connect to the right database (e.g JTS against the JTS DB and RTC against the RTC/CCM db) you can follow the hint in the error message to reset the lock ID to connect to the database. From the error message in your post:

"Check the server configuration and the database connection spec and ensure they are correct. To recover from an emergency lockout, the lock can be reset using the 'repotools -resetRepoLockId' command."

Thanks for the answer. I finally figured it out - I didn't have the right jdbc driver - once I got that corrected, I got past that point.

So you had the wrong DB driver and that caused the error? Good to know! Thanks for sharing.

We had the same problem. The teamserver properties file had DERBY hard coded. So when we used repotools, it was unlocking the DERBY database. However, our Jazz databases are on SQL Server. So we modified the teamserver file and entered SQL Server and then ran reptools. That fixed the issue.

I have a question for Kunal.  I am running in a similar problem where I am trying to load a Dev Database in to a newly installed CLM installation.  This Dev Database was used in another environment, but it was copied over to a Production Database which made this database available for a test environment.  When running JTS/setup I get the lockid issue.  I run the resetRepoLockId command and I get the info about Derby, because that is the default in the teamserver.properties file.  We are using SQL Server and I tried editing the teamserver.properties but that led in to a different error and then I changed it again and then I went downhill from there.  So I have cleaned up the environment and back to a clean install and trying to again add the SQL database.  Before I take any more steps, what edits were added to the default teamserver.properties file to change it to SQL?