- Create a new database with the appropriate character set and collation. For the database-specific information, see PostgreSQL, MySQL
MS SQL. If you are using MySQL or MS SQL, we recommend using the case-sensitive collation to avoid issues with agents on Unix-like OS.
- Copy the current
<TeamCity Data Directory>/config/database.propertiesfile, and change the database references in the copy to the newly created database.
- Stop the TeamCity server.
- Use the
maintainDBtool to migrate to the new database:
Depending on the size of your database, the migration may take from several minutes to several hours. For more information on the
maintainDB migrate [-A <path-to-data-dir>] -T <new-database-properties-file>
maintainDB tool, see this section.
- Upon the successful completion of the database migration, the
maintainDBtool should update the
<TeamCity Data Directory>/config/database.propertiesfile with references to the new database. Ensure that the file has been updated. Edit the file manually if the tool fails to do it automatically.
- Start the TeamCity server.
Protocol violation error (Oracle only)
This error can occur when the Oracle JDBC driver is not compatible with Oracle server. For example, Oracle JDBC driver version 11.1 is not compatible with Oracle server version 10.2.
In order to resolve the problem, just use Oracle JDBC driver from your Oracle server installation, or download driver of the same version as Oracle server.
Common Maven issues
There are two kinds of Maven-related issues commonly seen in the TeamCity build configurations: