Upgrading JTS server from 3.0.1 to 3.1.1.3 issue #2 thread
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.
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.
3 answers
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.
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.
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/rmThe 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
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."
"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."
Comments
Zulchefil Ozgian
Jun 08 '12, 5:03 a.m.Zulchefil Ozgian
Jun 08 '12, 5:03 a.m.Zulchefil Ozgian
Jun 08 '12, 5:03 a.m.Zulchefil Ozgian
Jun 08 '12, 5:03 a.m.Zulchefil Ozgian
Jun 08 '12, 5:04 a.m.Zulchefil Ozgian
Jun 08 '12, 5:04 a.m.Zulchefil Ozgian
Jun 08 '12, 5:04 a.m.Zulchefil Ozgian
Jun 08 '12, 5:04 a.m.Zulchefil Ozgian
Jun 11 '12, 4:48 a.m.Zulchefil Ozgian
Jun 11 '12, 6:01 a.m.