The first major change that's executed in this substage is a database migration. Artifactory converts its database schema from its current version to an upgraded schema:
This SQL conversion is automated. The Artifactory code was written with the expectation that the exact database schema of the preupgrade Artifactory version is in place. This automation performs the upgrade in separate steps, the exact SQL commands will vary depending on the detected starting version. Each version of Artifactory builds on these steps, an upgrade from 5.4 to 6.4 will start with the same steps as upgrading from 5.4 to 5.5 and add additional SQL.
Of all the stages, this is the one that's most likely to be the cause of an upgrade failure due to the hard-coded nature of these changes mentioned earlier. Troubleshooting this step is described below in Troubleshooting section 3B.
[Artifactory.log - Derby database conversion] 2019-09-10 20:57:15,376 [art-init] [INFO ] (o.a.s.d.v.ArtifactoryDBVersion:121) - Starting database conversion from 6.5.18(60518900) to 6.12.1(61201900) 2019-09-10 20:57:15,380 [art-init] [INFO ] (o.a.s.d.v.c.DbSqlConverterUtil:93) - Starting schema conversion: /conversion/derby/derby_v214_replication_errors.sql [...] 2019-09-10 20:57:15,579 [art-init] [INFO ] (o.a.s.d.v.c.DbSqlConverterUtil:95) - Finished schema conversion: /conversion/derby/derby_v218_add_bundle_files_idx.sql 2019-09-10 20:57:15,580 [art-init] [INFO ] (o.a.s.d.v.ArtifactoryDBVersion:125) - Finished database conversion from 6.5.18(60518900) to 6.12.1(61201900)
This SQL conversion is automated. The Artifactory code was written with the expectation that the exact database schema of the preupgrade Artifactory version is in place. This automation performs the upgrade in separate steps, the exact SQL commands will vary depending on the detected starting version. Each version of Artifactory builds on these steps, an upgrade from 5.4 to 6.4 will start with the same steps as upgrading from 5.4 to 5.5 and add additional SQL.
Of all the stages, this is the one that's most likely to be the cause of an upgrade failure due to the hard-coded nature of these changes mentioned earlier. Troubleshooting this step is described below in Troubleshooting section 3B.