Error upgrading external DB schema during TC7 upgrade

Hi guys,

During upgrade TCv6.0.3 to TCv7.0.1 on Linux using external DB I've got following error:
Error.bmp

,which seams caused by attempt to acquire DB lock:

[2012-04-04 11:29:39,854]   INFO -   jetbrains.buildServer.SERVER - Initializing working state...
[2012-04-04 11:29:40,329]   INFO - ide.db.TeamCityDatabaseManager - Attempt to capture TeamCity DB lock (java thread 112, starting code 1647976457, attempt 1)
[2012-04-04 11:29:43,473]   INFO - ide.db.TeamCityDatabaseManager - The TeamCity DB lock is not captured (java thread 112, starting code 1647976457, attempt 1)
[2012-04-04 11:29:50,478]   INFO - ide.db.TeamCityDatabaseManager - Attempt to capture TeamCity DB lock (java thread 112, starting code 1647976457, attempt 2)
[2012-04-04 11:29:53,635]   INFO - ide.db.TeamCityDatabaseManager - The TeamCity DB lock is not captured (java thread 112, starting code 1647976457, attempt 2)
[2012-04-04 11:30:00,804]   WARN - ide.db.TeamCityDatabaseManager - TeamCity server that is currently working:
        Starting code = 577182350
        Starting time = 2012-04-04 11:19:52.0
        IP address = XXX.XXX.XXX.XXX
        Application info = Apache Tomcat/6.0.14-ubsib_04
[2012-04-04 11:30:00,806]  ERROR -   jetbrains.buildServer.SERVER - Attempt to start more than one TeamCity server connected to the same database.


I have one TCv6.0.3 running instance, which uses external Oracle DB:
connectionUrl=jdbc:oracle:thin:@xxx:1528:ABC
connectionProperties.user=USER1
connectionProperties.password=USER1


And I'm trying to upgrade another TCv6.0.3 instance, which uses another DB schema on same DB server:
connectionUrl=jdbc:oracle:thin:@xxx:1528:ABC
connectionProperties.user=USER3
connectionProperties.password=USER3

I'm wondered if upgrade of one Oracle schema required lock for entire database.

Could someone please clarify DB upgrade procedure or suggest some solution?


If suggestion will be to stop first running instance while upgrading second instance, can we be sure that USER1 schema will not be affected by USER3 schema upgrade process?

Thank you,
Oleg
1 comment
Comment actions Permalink

The problem solved.
The problem was that in webapps folder I had two folders with old TCv6.0.3 binaries and new TCv7.0.1 binaries.
It caused Tomcat was trying to run two instances at once...

0

Please sign in to leave a comment.