Locate upgrade scripts folder in distribution zip file. For example, /database/oracle/upgrade, /database/postgres/upgrade, /database/mysql/upgrade. This . This folder(s) includes a number of folders containing migration.sql, which upgrade the FlexDeploy schemas.
Warning | |||||||
---|---|---|---|---|---|---|---|
This documentation is for upgrade to FlexDeploy to 5.3 but this statement may still apply if your upgrading from version prior to FlexDeploy 5.1. FlexDeploy 5.1 migration included As part of FlexDeploy 5.4 upgrade, missing UK constraint was added for REL_METADATA_VALUE table. Please check that there are no duplicate rows by running following SQL prior to upgrade. If you find duplicates then contact us via support portal.
|
Warning | |||||||
---|---|---|---|---|---|---|---|
If you are upgrading from version prior to FlexDeploy 5.2, run following SQL prior to running upgrade scripts and make sure no rows are returned. If there are any row returned, it is possible that migration may not work correctly, in which case contact us via support portal.
|
Warning | |||||||
---|---|---|---|---|---|---|---|
FlexDeploy 5.1 migration includes updates to Unique Constraint for FF.DB_PROPERTIES_DATA. If you are upgrading from version prior to 5.1, then run following SQL before running upgrade scripts. If you have duplicates then it needs to be fixed up prior to starting migration. Run following SQL to check if there are any duplicates. If there are duplicates, work with Flexagon support team to resolve prior to migration.
|
You will need to execute one or more SQL script(s) from the version of FlexDeploy you currently have, up to the latest version. And they must be executed in that order.
Follow this guideline when deriving SQL files to be executed.
...
Info |
---|
There is not an upgrade script for every version. For instance there is no upgrade script for upgrading FlexDeploy 5.6.0.0 or higher
Current version is before 4.6.0.0
6 to FlexDeploy 5.7.0.0. Simply skip to the next one needed, or stop if there aren't anymore. |
See some examples below to help you understand database upgrade process.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
v5.23.0.0-to-5.2.0.1v5.3.0.2/migration.sql v5.3.0.2-to-v5.3.0.3/migration.sql v5.23.0.13-to-5v5.3.0.04/migration.sql | ||||||
Code Block | ||||||
language | sql | title | Upgrading 5.1v5.3.0. | 0 4-to | 5-v5. | 34.0.0 |
linenumbers | true | /migration.sql v5.14.0.0-to-5v5.14.0.31/migration.sql v5.14.0.31-to-v5.24.0.03/migration.sql v5.24.0.03-to-5v5.24.0.14/migration.sql v5.24.0.14-to-v5.5.3.0.0/migration.sql |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
v5.04.0.0-to-v5.14.0.01/migration.sql v5.14.0.01-to-5v5.14.0.3/migration.sql v5.14.0.3-to-v5.24.0.04/migration.sql v5.24.0.04-to-v5.5.0.0/migration.sq |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
v5.4.0.1-to-v5.4.0.3/migration.sql v5.2.4.0.3-to-v5.4.0.4/migration.sql v5.4.0.14-to-v5.5.3.0.0/migration.sql |
Executing migration files
...