Upgrading JTS server from 3.0.1 to 3.1.1.3 issue #2 thread

Question

Now I have followed your suggestion and deleted the repositoryDB from the newest 3.1.1.3 instalation directory and copied over again from 3.0.1 for each of them (jts,ccm,rqm)

I have another error now.

[root@oc0570384574 server]# ./repotools-jts.sh -addTables noPrompt
Repo Tools
Provisioning using "./conf/jts/provision_profiles".
Jazz Foundation - Core Libraries, Version 3.0.1.3 (RJF-I20120322-1607)

CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
CRJAZ1779I This server is configured as a JTS.
CRJAZ1971I The server is configured with:
Public URI: "https://oc0570384574.ibm.com:9443/jts"
CRJAZ1365I The server is attempting to connect to the following database: "conf/jts/derby/repositoryDB"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Apache Derby
Db Product Version: 10.5.3.2 - (1073208)
Db URL: jdbc:derby:conf/jts/derby/repositoryDB;create=true
Jdbc Driver Name: Apache Derby Embedded JDBC Driver
Jdbc Driver Version: 10.5.3.2 - (1073208)
CRJAZ8192I: Fulltext Index Location: /opt/IBM/JazzTeamServer_1/server/conf/jts/indices/workitemindex/fulltext_index
CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set to 'conf/jts/indices/workitemindex'
Adding tables to the database "conf/jts/derby/repositoryDB".
CRJAZ1442I The component model of "com.ibm.team.repository.auth" was updated from "3" to "4".
CRJAZ1770E 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 team server.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.
The user "ADMIN" has logged out of the database "conf/jts/derby/repositoryDB".
CRJAZ1728E An unexpected error has been detected. See the log file opt/IBM/Jaz zTeamServer_1/server/repotools-jts_addTables.log" for more details.

Answer 1

All I can say is that you got yourself into a bad state, where the 3.0.1.3 properties files are not consistent with the 3.0.1.3 databases. If your 3.0.1 server still runs without any problems connecting to the database, then I suggest starting over - delete the 3.0.1.3 repositoryDB folders again, copy the 3.0.1 repositoryDB folders to the 3.0.1.3 server install area, copy the properties files again.

Or, if you want to try a shortcut, you can do what the error message suggests: execute 'repotools-jts -resetRepoLockId' (in the 3.0.1.3 server area) to reset the lock id.

Answer 2

0

permanent link

John Vasta (2.6k●1●5) | answered Jun 08 '12, 8:22 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

It sounds like the 3.0.1 teamserver.properties files, and all the other configuration files, did not get copied correctly from the 3.0.1 install area to the 3.0.1.3 install area. This is step 8 in the upgrade procedure:

cp 3.0.1_install_dir/server/conf/jts/teamserver*.properties  3.0.1.x_install_dir/server/conf/jts
cp 3.0.1_install_dir/server/conf/ccm/teamserver*.properties  3.0.1.x_install_dir/server/conf/ccm
cp 3.0.1_install_dir/server/conf/qm/teamserver*.properties  3.0.1.x_install_dir/server/conf/qm
cp 3.0.1_install_dir/server/conf/admin/admin.properties*  3.0.1.x_install_dir/server/conf/admin
cp 3.0.1_install_dir/server/conf/admin/friends.rdf*  3.0.1.x_install_dir/server/conf/admin
cp 3.0.1_install_dir/server/conf/rm/fronting.properties  3.0.1.x_install_dir/server/conf/rm
cp 3.0.1_install_dir/server/conf/rm/friendsconfig.rdf  3.0.1.x_install_dir/server/conf/rm

The repository lock ids are stored in the teamserver.properties file for each product, and they must match what is stored in the database. So if you copy both the databases and the teamserver.properties files correctly, they should still match. Therefore, please do the above copy commands again, and verify that the files got copied correctly and are in the correct location. Then retry the addTables command.

Comments

Zulchefil Ozgian commented Jun 08 '12, 8:31 a.m. | edited Jun 11 '12, 9:17 a.m.

I have done what you said and now this error I get

[root@oc0570384574 server]# ./repotools-jts.sh -addTables noPrompt
Repo Tools
Provisioning using "./conf/jts/provision_profiles".
Jazz Foundation - Core Libraries, Version 3.0.1.3 (RJF-I20120322-1607)

CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
CRJAZ1779I This server is configured as a JTS.
CRJAZ1971I The server is configured with:
Public URI: "https://oc0570384574.ibm.com:9443/jts"
CRJAZ1365I The server is attempting to connect to the following database: "conf/jts/derby/repositoryDB"
CRJAZ1364I The connection to the following database was successful:
Db Product Name: Apache Derby
Db Product Version: 10.5.3.2 - (1073208)
Db URL: jdbc:derby:conf/jts/derby/repositoryDB;create=true
Jdbc Driver Name: Apache Derby Embedded JDBC Driver
Jdbc Driver Version: 10.5.3.2 - (1073208)
CRJAZ8192I: Fulltext Index Location: /opt/IBM/JazzTeamServer_1/server/conf/jts/indices/workitemindex/fulltext_index
CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set to 'conf/jts/indices/workitemindex'
Adding tables to the database "conf/jts/derby/repositoryDB".
CRJAZ1442I The component model of "com.ibm.team.repository.auth" was updated from "3" to "4".
CRJAZ1770E 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.
The user "ADMIN" has logged out of the database "conf/jts/derby/repositoryDB".
CRJAZ1728E An unexpected error has been detected. See the log file "/opt/IBM/JazzTeamServer_1/server/repotools-jts_addTables.log" for more details.

Zulchefil Ozgian commented Jun 08 '12, 8:33 a.m. | edited Jun 11 '12, 9:17 a.m.

2012-06-08 15:29:50,759 Repo Tools
2012-06-08 15:29:50,760 java.version=1.5.0
2012-06-08 15:29:50,760 java.runtime.version=pxi32devifx-20110209 (SR11 FP2 +IZ94331)
2012-06-08 15:29:50,763 Provisioning using "./conf/jts/provision_profiles".
2012-06-08 15:29:50,780 repotools-jts -addTables noPrompt
2012-06-08 15:29:50,781 Jazz Foundation - Core Libraries, Version 3.0.1.3 (RJF-I20120322-1607)

2012-06-08 15:29:50,790 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
2012-06-08 15:29:51,292 CRJAZ1779I This server is configured as a JTS.
2012-06-08 15:29:51,293 CRJAZ1971I The server is configured with:
Public URI: "https://oc0570384574.ibm.com:9443/jts"
2012-06-08 15:29:53,550 CRJAZ1365I The server is attempting to connect to the following database: "conf/jts/derby/repositoryDB"
2012-06-08 15:29:53,936 CRJAZ1364I The connection to the following database was successful:
Db Product Name: Apache Derby
Db Product Version: 10.5.3.2 - (1073208)
Db URL: jdbc:derby:conf/jts/derby/repositoryDB;create=true
Jdbc Driver Name: Apache Derby Embedded JDBC Driver
Jdbc Driver Version: 10.5.3.2 - (1073208)
2012-06-08 15:29:55,074 CRJAZ8192I: Fulltext Index Location: /opt/IBM/JazzTeamServer_1/server/conf/jts/indices/workitemindex/fulltext_index
2012-06-08 15:29:55,074 CRJAZ8190I: The fulltext index should point to an absolute directory but is currently set to 'conf/jts/indices/workitemindex'
2012-06-08 15:29:56,736 Removing project move component...
2012-06-08 15:29:56,741 Removed project move component in 7 ms.
2012-06-08 15:29:56,741 Adding tables to the database "conf/jts/derby/repositoryDB".
2012-06-08 15:29:58,022 CRJAZ1442I The component model of "com.ibm.team.repository.auth" was updated from "3" to "4".
2012-06-08 15:29:58,466 CRJAZ1770E 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.

Zulchefil Ozgian commented Jun 08 '12, 8:34 a.m. | edited Jun 11 '12, 9:17 a.m.

2012-06-08 15:29:58,468 The user "ADMIN" has logged out of the database "conf/jts/derby/repositoryDB".
2012-06-08 15:29:59,912 CRJAZ1770E 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 t
o 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 conne
ction 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 infor
mation on the affected database.
java.lang.RuntimeException: CRJAZ1770E 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 tryi
ng 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 c
onnection 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 i
nformation on the affected database.
        at com.ibm.team.repository.service.internal.rdb.DatabaseStateService.refreshState(DatabaseStateService.java:73)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at <unknown class>.<unknown method>(Unknown Source)

Zulchefil Ozgian commented Jun 08 '12, 8:34 a.m. | edited Jun 11 '12, 9:18 a.m.

        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.refreshDatabaseState(AddTablesCommand.java:95)
        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.addTables(AddTablesCommand.java:63)
        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.execute(AddTablesCommand.java:137)
        at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:64)
        at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:736)
        at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:811)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1287)

Zulchefil Ozgian commented Jun 08 '12, 8:34 a.m. | edited Jun 11 '12, 9:18 a.m.

Caused by:
com.ibm.team.repository.common.TeamRepositoryException: Server lock id value _Z0dRAF4FEeGVJNmZLFfWHQ and database lock id _DaHSQV4CEeGbaM_FU-mS2Q do not match for database jdbc:d
erby:conf/jts/derby/repositoryDB. Use the 'repotools-jts -resetRepoLockId' command to remove the DB lockID, after ensuring this DB is not used by another JTS or application.
        at com.ibm.team.repository.service.internal.db.util.RepoLockIdUtil.checkServerToSchemaLock(RepoLockIdUtil.java:181)
        at com.ibm.team.repository.service.internal.db.util.RepoLockIdUtil.checkServerToSchemaLock(RepoLockIdUtil.java:148)
        at com.ibm.team.repository.service.internal.rdb.DatabaseStateService.checkServerLockToSchemaLock(DatabaseStateService.java:109)
        at com.ibm.team.repository.service.internal.rdb.DatabaseStateService.refreshState(DatabaseStateService.java:65)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:618)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at <unknown class>.<unknown method>(Unknown Source)
        ... 19 more
2012-06-08 15:29:59,913 CRJAZ1728E An unexpected error has been detected. See the log file "/opt/IBM/JazzTeamServer_1/server/repotools-jts_addTables.log" for more details.

Answer 3

There is a mismatch of the lock ID of the database and the teamserver.properties. If you are sure you work against the right database, you can use the repotools command suggested in the error message to delete the lock files. The lock is used to prevent from accidentally run more than one server against the same database. You want to really make sure the teamserver.properties of JTS, CCM, QM refer to different databases.

"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."

It's all about the answers!

Related questions

Upgrading JTS server from 3.0.1 to 3.1.1.3 issue #2 thread

3 answers

Your answer