FlexDeploy Schema Upgrade

From the downloaded distribution, extract the /database/upgrade folder.  This folder includes a number of 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.  For example, if you are upgrading from FlexDeploy 3.7.1 to FlexDeploy 4.0.3, you will need to execute migration3.7.1_to_4.0.0.sql, then migration4.0.0_to_4.0.1.sql, then migration4.0.1_to_4.0.2.sql, and finally, migration4.0.2_to_4.0.3.sql. The migration4.0.2_to_4.0.3.sql file includes all of the 403PatchRelease*.sql files in it. Patch Release SQL files are only necessary if you are already on previous 4.0.3 Patch Release.

If you are upgrading from 4.0.2. to 4.0.3, run migration4.0.2_to_4.0.3.sql.

If you are upgrading from a 4.0.3 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 About window of your FlexDeploy installation. Contact Flexagon support for details if you are not sure. See example below.

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.

sqlplus

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.

To launch sqlplus:

export ORACLE_HOME=<your Oracle Home directory>
export ORACLE_SID=<the SID of your database>
spool migration4.0.3.out #(change for each script execution so logs are preserved)
$ORACLE_HOME/bin/sqlpus #(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:

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

For example,