The configured database lock id does not match the lock id in the database
Piotr Aniola (3.7k●1●17●38)
| asked Mar 21 '14, 8:09 a.m.
edited Mar 26 '14, 3:56 p.m. by Stephanie Taylor (241●1●5)
Hello,
I'm trying to attach RQM to a restored DB. RQM is 4.0.5, DB is DB2 9.7. When doing test connection in the setup wizard I'm getting: "The configured database lock id does not match the lock id in the database. This can happen if 2 applications or Jazz Team Servers are trying to access the same set of tables, or if the lock id was overwritten or lost in the teamserver.properties configuration file. 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. Check the log file for information on the affected database. |
Accepted answer
Hi Piotr - you are running the correct command, but in the first line you mention "DB2", but all the resetRepoLockId commands you are running are connecting to the local Derby instance, e.g.:
Piotr Aniola selected this answer as the correct answer
Comments
Piotr Aniola
commented Mar 25 '14, 8:54 a.m.
You are right, and that fixed it, but it doesn't explain why there was the repoLockId issue in the first place. I suppose the setup wizard tests the DB against the default DB from the teamserver.properties, rather than the values from entered in the wizard
|
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.