...
| Tip |
|---|
If you are upgrading from 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 If you are upgrading from version earlier than 4.6.0.0, then it is necessary to compare Build Time as well to determine execution of migration SQL files. |
Image Removed
Image Added
Follow this guideline when deriving SQL Patches to be applied.
...
See some examples below to help you understand database upgrade process.
...
.
| Code Block |
|---|
| language | sql |
|---|
| title | Upgrading 45.60.0.0 (or 45.60.0.x) to 5.01.0.0 |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
v4.6v5.0.0.0-to-4v5.61.10.0/migration.sql
v4 |
| Code Block |
|---|
| language | sql |
|---|
| title | Upgrading 4.6. |
|---|
| 1 | -to- | .2 | /migration.sql
| .0 | | linenumbers | true |
|---|
| collapse | true |
|---|
|
v4.6.20.0-to-4v5.60.30.0/migration.sql
v4v5.60.30.0-to-5v5.01.0.0/migration.sql
|
| Code Block |
|---|
| language | sql |
|---|
| title | Upgrading 4.0 to 5.0.0.0 |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
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
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 |
|---|
| language | sql |
|---|
| title | Upgrading 4.0.3 (build time 4/23/2017 or earlier) to 5.0.0.0 |
|---|
| 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
v4.0.3-to-v4.5.0/migration.sql
v4.5.0-to-v4.6.0.0/migration.sql
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
5.0-to-v4.6.3.0-to-5.0.0.0/migration.sql |
| Code Block |
|---|
| language | sql |
|---|
| title | Upgrading 4.0.3 (build time 5/11/2017) to 5.0.0.0 |
|---|
| 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
v4.0.3-to-v4.5.0/migration.sql
v4.5.0-to-v4.6.0.0/migration.sql
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
5.0-to-v4.6.3.0-to-5.0.0.0/migration.sql |
| Code Block |
|---|
| language | sql |
|---|
| title | Upgrading 4.5.1 Patch Release 11-27-2017 to 5.0.0.0 |
|---|
| linenumbers | true |
|---|
| collapse | true |
|---|
|
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
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 |
Executing migration files
These scripts should be executed as system, sys, 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. Following is example of script execution for Oracle, for PostgreSQL & MySQL use appropriate tools to execute migration scripts.
| Info |
|---|
|
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 |
|---|
| 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 |
|---|
| 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>> |
|
...