...
Check Compatibility Guide and Upgrade Planning to ensure that your version of database, Tomcat tomcat and Java java are supported in the planned upgrade. If any of these items need updating, please contact your IT team several weeks in advance of the planned upgrade.
Java upgrades
If java needs upgrading, you must verify that any JDBC connectors you have installed to non-standard databases are still supported. The standard databases supported by PhixFlow are Oracle, MS SQL Server and MySQL/ MariaDB. The drivers needed to connect to these databases are shipped with PhixFlow, and connections to external databases though PhixFlow datasources are supported by these drivers. However, if you have connections to external databases other than these - for example, Netezza, Teradata, DB2 - then you will have installed JDBC drivers for these in the folder
| Code Block |
|---|
[tomcat home]/lib |
You must check that your current version of each installed driver is compatible with the new version of java, and if not, obtain a new version of the JDBC driver from the supplier.
Special upgrade instructions
Also check Compatibility Guide and Upgrade Planning for any special upgrade instructions between your current and target versions.
...
Remember, if you are upgrading tomcat, to restore any JDBC drivers needed for datasources that use database technologies or versions not supported for PhixFlow's own connections. See Install Tomcat Installation for details, but in brief, make sure that any additional JDBC drivers you use are placed in:
...
Run all migration scripts run in sequence from the starting version to this version e.g.:.
| Note | ||
|---|---|---|
| ||
Please note that some of the scripts can generate warning messages. One example of this is Caution: Changing any part of an object name could break scripts and stored procedures. Generally, these warning messages do not indicate a problem. However, in the event that you see any error messages, please contact your PhixFlow support team. |
Oracle
E.g. for Oracle users:
| Code Block |
|---|
cd $RELEASE/schema/oracle/migration/X.Y sqlplus myUsername/myPassword @migrate_schema_from_x_y_z_to_X_Y_Z.sql |
SQL Server
E.g. for SQL Server users:
| Code Block |
|---|
cd $RELEASE/schema/sqlserver/migration/X.Y sqlcmd -S myServer\myInstance -U myUsername -P myPassword -d myDatabase -i migrate_schema_from_x_y_z_to_X_Y_Z.sql |
| Note | ||
|---|---|---|
| ||
Please note that some of the scripts can generate warning messages. One example of this is Caution: Changing any part of an object name could break scripts and stored procedures. These warning messages are normal and do not indicate a problem. However, in the unlikely event that you see an error message, please contact your PhixFlow support team. |
...
MariaDB (MySQL)
| Warning |
|---|
Some MariaDB PhixFlow migration scripts create or use privileged functions and/or procedures, and must have privileges not required by the regular PhixFlow user. Specifically, one of the following must be true:
If neither are true, the migration script may fail and would require manual recovery. |
| Code Block | ||
|---|---|---|
| ||
cd $RELEASE/schema/sqlserver/migration/X.Y
mysql -h myServer -u myUsername -p -D myDatabase
source migrate_schema_from_x_y_z_to_X_Y_Z.sql |
Re-start Tomcat
Import new Templates package
See Import Templates and Formats for guidelines on whether or not, and how to import the templates file.
Complete
The upgrade is now complete.