Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

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.

Code Block
languagesql
themeRDark
SELECT
    kd.property_key_name, k.*
FROM
    fd.property_key k,
    fd.property_key_definition kd,
    fd.property_value pv
WHERE
    k.property_definition_id = kd.property_definition_id
    AND pv.sequence_number = 0
    AND k.property_key_id = pv.property_key_id
    AND kd.is_encrypted = 'Y'
    AND k.is_encrypted = 'N'
    AND pv.property_value not in ('<NOT CONFIGURED>', '<OPTIONAL>');



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. If there are duplicates, work with Flexagon support team to resolve prior to migration.

Code Block
languagesql
themeRDark
SELECT * FROM (SELECT DB_PROPERTIES_ID, SEQUENCE_NUMBER, COUNT(1) NUMROWS
FROM FF.DB_PROPERTIES_DATA 
GROUP BY DB_PROPERTIES_ID, SEQUENCE_NUMBER) 
WHERE NUMROWS>1;


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.

Image RemovedImage Added

Info

There is not an upgrade script for every version. For instance there is no upgrade script for upgrading FlexDeploy 5.6.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
languagesql
titleUpgrading 5.23.0.0 to 5.45.0.0
linenumberstrue
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.4/migration.sql
v5.3.0.4-to-v5.4.0.0/migration.sql
v5.34.0.0-to-v5.34.0.21/migration.sql
v5.34.0.21-to-v5.34.0.3/migration.sql
v5.34.0.3-to-v5.34.0.4/migration.sql
v5.34.0.4-to-v5.45.0.0/migration.sql


Code Block
languagesql
titleUpgrading 5.34.0.0 to 5.45.0.0
linenumberstrue
v5.34.0.0-to-v5.34.0.21/migration.sql
v5.34.0.21-to-v5.34.0.3/migration.sql
v5.34.0.3-to-v5.34.0.4/migration.sql
v5.34.0.4-to-v5.45.0.0/migration.sql sq


Code Block
languagesql
titleUpgrading 5.34.0.2 to 5.45.0.0
linenumberstrue
v5.34.0.21-to-v5.34.0.3/migration.sql
v5.34.0.3-to-v5.34.0.4/migration.sql
v5.34.0.4-to-v5.45.0.0/migration.sql 

Executing migration files

...