Versions Compared

Key

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

From the downloaded distributionzip file, extract the /database/oracle/upgrade folder. This folder includes a number of folders containing migration.sql sql and patch release 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

Tip

If you are upgrading from

...

If you are upgrading 4.6 then you need to run some SQL files as well.

...

4.6.0.0 or higher then you can just look at Build Version in About window and use that information to derive SQL files to be executed. Previously, it was necessary to compare Build Time as well.

Image Added

Info
titleDeriving SQL Patches applied

Current version is 4.6.0.0 or higher

  • Look at Build Version in About window.

Current version is before 4.6.0.0

  • 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.
  • Or you can view list of patches by using Administration - FlexDeploy Patches in FlexDeploy.

See some examples below to help you understand database upgrade process.

Code Block
languagesql
titleUpgrading 4.6.0.0 (or 4.6.0.x) to 5.0.0.0
linenumberstrue
collapsetrue
v4.6.0.0-to-4.6.1.0/migration.sql
v4.6.1.0-to-4.6.2.0/migration.sql
v4.6.2.0-to-4.6.3.0/migration.sql
v4.6.3.0-to-5.0.0.0/migration.sql


Code Block
languagesql
titleUpgrading 4.0 to 4.6.0.0
linenumberstrue
collapsetrue
v4.0-to-v4.0.1/migration.sql
v4.0.1-to-v4.0.2/migration.sql
v4.0.2-to-v4.0.3/migration.sql
v4.0.3-to-v4.5.0/migration.sql
v4.5.0-to-v4.6.0.0/migration.sql

...

Code Block
languagesql
titleUpgrading 4.5.1 Patch Release 11-27-2017 to 4.6.0.0
linenumberstrue
collapsetrue
v4.0.3-to-v4.5.0/450PatchRelease_12-09-2017.sql
v4.0.3-to-v4.5.0/450PatchRelease_01-12-2018.sql
v4.0.3-to-v4.5.0/450PatchRelease_01-30-2018.sql
v4.5.0-to-v4.6.0.0/migration.sql
Info
titleDeriving 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.

Or you can view list of patches by using Administration - FlexDeploy Patches in FlexDeploy.

Image Removed

Executing migration files

These scripts should be executed as systemsys, or another user which has privileges to create objects in other schemas, performs grants, etc.  You can load and execute these scripts using other tools such as Toad or SQL Developer, but the instructions here are for using the sqlplus client.

Info
titlesqlplus

Oracle sqlus is part of the Oracle Client, and may be executed on any host which has it installed. If the Oracle Client is not installed on the same host as where you are installing FlexDeploy, you can copy the scripts to another host which has it installed.

Make sure to spool output to a file, so it can be analyzed later if necessary.

To launch sqlplus:

Code Block
languagebash
export ORACLE_HOME=<your Oracle Home directory>
export ORACLE_SID=<the SID of your database>
spool migration4.5.0.out #(change for each script execution so logs are preserved)
$ORACLE_HOME/bin/sqlplus #(login as sys or system when prompted)
SQL> <<execute scripts as shown above>>

If running on another host other than the database server, you must update your tnsnames file and and launch sqlplus as follows:

Code Block
languagebash
export ORACLE_HOME=<your Oracle Home directory>
export ORACLE_SID=<the SID of your database>
spool migration4.5.0.out #(change for each script execution so logs are preserved)
$ORACLE_HOME/bin/sqlplus system@<tnsname>
SQL> <<execute scripts as shown above>>


...