You are viewing the documentation of TeamCity 8.x, which is not the most recently released version of TeamCity.
Go to the latest TeamCity documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Protocol violation error (Oracle only)


  1. 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.
  2. Copy the current <TeamCity Data Directory>/config/database.properties file, and change the database references in the copy to the newly created database.
  3. Stop the TeamCity server.
  4. Use the maintainDB tool to migrate to the new database:
    Code Block
    maintainDB migrate [-A <path-to-data-dir>] -T <new-database-properties-file>
    Depending on the size of your database, the migration may take from several minutes to several hours. For more information on the maintainDB tool, see this section.
  5. Upon the successful completion of the database migration, the maintainDB tool should update the <TeamCity Data Directory>/config/database.properties file 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.
  6. Start the TeamCity server.

Back to top

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: