SQL exception: error in script file line: 212 out of memory

Permanently deleted user

Created July 18, 2014 18:47

Admittedly, it's been a few weeks since I checked on our build server, but I find that it went down. I restarted the machine, and it's still down.

I get the following message after entering the appropriate token:

Any suggestions???
--Eric

TeamCity has failed to start

TeamCity server startup error

Error Details

Stacktrace copied

jetbrains.buildServer.serverSide.db.UnexpectedDBException: Unexpected exception SQLException: SQL error when doing: Taking a connection from the data source
SQL exception: error in script file line: 212 out of memory
     at org.hsqldb1.jdbc.Util.sqlException(Util.java:63)
     at org.hsqldb1.jdbc.jdbcConnection.<init>(jdbcConnection.java:2427)
     at org.hsqldb1.jdbcDriver.getConnection(jdbcDriver.java:183)
     at org.hsqldb1.jdbcDriver.connect(jdbcDriver.java:161)
     at jetbrains.buildServer.serverSide.db.jdbcLoader.JdbcDataSource.getConnection(JdbcDataSource.java:52)
     at jetbrains.buildServer.serverSide.db.DBFunctions.create(DBFunctions.java:231)
     at jetbrains.buildServer.serverSide.db.TeamCityDatabaseManager.connect(TeamCityDatabaseManager.java:318)
     at jetbrains.buildServer.maintenance.StartupProcessor.performConnectToDatabaseInternal(StartupProcessor.java:218)
     at jetbrains.buildServer.maintenance.StartupProcessor.performConnectToDatabase(StartupProcessor.java:305)
     at jetbrains.buildServer.maintenance.StartupProcessor.doDatabaseConnect(StartupProcessor.java:425)
     at jetbrains.buildServer.maintenance.StartupProcessor.processConcreteStage(StartupProcessor.java:376)
     at jetbrains.buildServer.maintenance.StartupProcessor.processConcreteStageSafe(StartupProcessor.java:486)
     at jetbrains.buildServer.maintenance.StartupProcessor.processTeamCityLifecycle(StartupProcessor.java:448)
     at jetbrains.buildServer.maintenance.StartupProcessor.access$000(StartupProcessor.java:450)
     at jetbrains.buildServer.maintenance.StartupProcessor$1.run(StartupProcessor.java:1)
     at java.lang.Thread.run(Thread.java:744)
caused by: java.sql.SQLException: error in script file line: 212 out of memory
     at org.hsqldb1.jdbc.Util.sqlException(Util.java:63)
     at org.hsqldb1.jdbc.jdbcConnection.<init>(jdbcConnection.java:2427)
     at org.hsqldb1.jdbcDriver.getConnection(jdbcDriver.java:183)
     at org.hsqldb1.jdbcDriver.connect(jdbcDriver.java:161)
     at jetbrains.buildServer.serverSide.db.jdbcLoader.JdbcDataSource.getConnection(JdbcDataSource.java:52)
     at jetbrains.buildServer.serverSide.db.DBFunctions.create(DBFunctions.java:231)
     at jetbrains.buildServer.serverSide.db.TeamCityDatabaseManager.connect(TeamCityDatabaseManager.java:318)
     at jetbrains.buildServer.maintenance.StartupProcessor.performConnectToDatabaseInternal(StartupProcessor.java:218)
     at jetbrains.buildServer.maintenance.StartupProcessor.performConnectToDatabase(StartupProcessor.java:305)
     at jetbrains.buildServer.maintenance.StartupProcessor.doDatabaseConnect(StartupProcessor.java:425)
     at jetbrains.buildServer.maintenance.StartupProcessor.processConcreteStage(StartupProcessor.java:376)
     at jetbrains.buildServer.maintenance.StartupProcessor.processConcreteStageSafe(StartupProcessor.java:486)
     at jetbrains.buildServer.maintenance.StartupProcessor.processTeamCityLifecycle(StartupProcessor.java:448)
     at jetbrains.buildServer.maintenance.StartupProcessor.access$000(StartupProcessor.java:450)
     at jetbrains.buildServer.maintenance.StartupProcessor$1.run(StartupProcessor.java:1)
     at java.lang.Thread.run(Thread.java:744)

Current Startup State

Startup status

Current step: TeamCity server startup error
Next step: not defined yet

Data Directory

Directory path: C:\TeamCityConfiguration\.BuildServer exists
Database properties file not found
Internal database file: 1.8.1

Database

Database type: default (using internal database)
Database connection URL: jdbc:hsqldb:file:$TEAMCITY_SYSTEM_PATH/buildserver

Versions

Software version: 658
Data directory version: 658
Database version: unknown

Logs

Logs path: C:\TeamCity\logs

1 comment

Alina Mishina

Created July 21, 2014 11:33

Hi,

Please try increasing server memory. If this does not help, most probably this means that you have encountered internal database corruption. You can try to deal with this corruption using the notes based on the HSQLDB documentation.
For more details please read this section.

Please sign in to leave a comment.