Artifactory must convert its existing database schema to the next version. This process is somewhat delicate because an Artifactory upgrade cannot proceed unless your database schema starts as an exact match of the hard-coded set of tables and indexes that the application has been set to change. To continue the upgrade, each SQL statement must succeed.
Artifactory expects an exact set of SQL Tables, Indexes, and Table Columns to match the old database schema when converting. Usually there is a JDBC SQL error in the logs that indicates the problem area.
Some common errors may result from manually adding an index file or table column to the database long before the upgrade was started. Depending on the error, undoing such changes may allow your upgrade to continue. One way to do this is by reloading a backup of the old version of Artifactory and attempt the upgrade again.
Please consult with your DBA and JFrog Support before manually modifying your Artifactory database or rolling back an upgrade.
Artifactory expects an exact set of SQL Tables, Indexes, and Table Columns to match the old database schema when converting. Usually there is a JDBC SQL error in the logs that indicates the problem area.
Some common errors may result from manually adding an index file or table column to the database long before the upgrade was started. Depending on the error, undoing such changes may allow your upgrade to continue. One way to do this is by reloading a backup of the old version of Artifactory and attempt the upgrade again.
Please consult with your DBA and JFrog Support before manually modifying your Artifactory database or rolling back an upgrade.