Versions Compared

Old Version 9

changes.mady.by.user Gary Parden

Saved on

compared with

New Version 10

changes.mady.by.user Gary Parden

Saved on

Key

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

...

Run all migration scripts run in sequence from the starting version to this version e.g.:.

Note
titleWarnings

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:

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.
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
titleWarnings

MariaDB (MySQL)

Warning

Some MariaDB migration scripts create or use privileged functions and/or procedures, and must have privileges not required by the regular PhixFlow user.

One of the following must be true:

  • the migration user must have SUPER privilege, or
  • the mysql global variable 'log_bin_trust_function_creators' must be set to true


Code Block
titleE.g. for MariaDB users
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

...