From the downloaded distribution, extract the /database/oracle/upgrade folder. This This folder includes a number of of folders containing migration*.sql files which upgrade the FlexDeploy schemas along with Patch Release SQL files.
You will need to execute these scripts from the version of FlexDeploy you currently have, up to the latest version. And they must be executed in that order. See examples below if you are upgrading from FlexDeploy 3.7.1 to FlexDeploy 4.5 or FlexDeploy 4.0.0 to FlexDeploy 4.5.
...
Code Block |
---|
language | sql |
---|
title | Upgrading 3.7.1 to 4.5 |
---|
linenumbers | true |
---|
collapse | true |
---|
|
migration3v3.7.1_-to_4-v4.0.0/migration.sql
migration4v4.0.0_to_4-to-v4.0.1/migration.sql
migration4v4.0.1_-to_4-v4.0.2/migration.sql
migration4v4.0.2_-to_4-v4.0.3/migration.sql
migration4v4.0.3_-to_4-v4.5.0/migration.sql |
Code Block |
---|
language | sql |
---|
title | Upgrading 4.0.0 to 4.5 |
---|
linenumbers | true |
---|
collapse | true |
---|
|
migration4v4.0.0_to_4-to-v4.0.1/migration.sql
migration4v4.0.1_-to_4-v4.0.2/migration.sql
migration4v4.0.2_-to_4-v4.0.3/migration.sql
migration4v4.0.3_-to_4-v4.5.0/migration.sql |
The migration44.0.2_-to_-4.0.3/migration.sql file includes all of the 403PatchRelease*.sql files in it. Patch Release SQL files are only necessary if you are on a 4.0.3 or 4.5.0 Release.
If you are upgrading from a 4.0.3 or 4.5.0 Patch Release, follow the date based SQL files in sequence by Date. If you have already a applied specific Patch Release patch then skip it. You can make determination of which Patch Release files to run by looking at Build Time on the About window of your FlexDeploy installation that you saved from a previous step. After completing the last 403PatchRelease, run the migration4.0.3_to_4.5.0.sql file. Contact Flexagon support for details if you are not sure. See example below.
Code Block |
---|
language | sql |
---|
title | Upgrading 4.0.3 (build time 4/23/2017 or earlier) to 4.5 |
---|
linenumbers | true |
---|
collapse | true |
---|
|
v4.0.2-to-v4.0.3/403PatchRelease_04-24-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_05-01-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_05-5-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_05-11-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_05-22-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_06-14-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_07-19-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_07-24-2017.sql
migration4v4.0.3_-to_4-v4.5.0/migration.sql |
Code Block |
---|
language | sql |
---|
title | Upgrading 4.0.3 (build time 5/11/2017) to 4.5 |
---|
linenumbers | true |
---|
collapse | true |
---|
|
v4.0.2-to-v4.0.3/403PatchRelease_05-22-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_06-14-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_07-19-2017.sql
v4.0.2-to-v4.0.3/403PatchRelease_07-24-2017.sql
migration4v4.0.3_-to_4-v4.5.0/migration.sql |
Info |
---|
title | Upgrade from 4.5 GA to 4.5 Patch Releases |
---|
| If you have 4.5 GA version installed and would like to upgrade to 4.5 patch releases like 4.5.1 or 4.5.2, then you will may need to run Patch Release SQL files that were not yet run on your database. Here is the current list of SQL patches on 4.5 GA.
- 450PatchRelease_10-11-2017.sql
- 450PatchRelease_11-01-2017.sql
- 450PatchRelease_11-02-2017.sql
- 450PatchRelease_12-09-2017.sql
- 450PatchRelease_01-12-2018.sql
Derive SQL Patches applied |
|
You can find which files that you may have already executed by doing "select version, created_on, created_by from fd.fd_flexdeploy_version order by created_on desc" database query. We have also added new screen in 4.5 patch release to Or you can view list of patches , which you can access by using Administration - FlexDeploy Patches in FlexDeploy. |
...