Skip to end of banner
Go to start of banner

Oracle upgrade guide

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Looking for the documentation on the newest versions of SIL Engine and the Simple Issue Language for Jira 8? Click here and leave these dusty old pages behind!

Because Oracle treats an empty string the same as a null value, and due to a bug in our upgrade task, it may happen that you loose some configuration from your database (e.g.: the SQL scripts longer that 255 characters from a database custom field). 

This issue affects versions 4.0.0 and 4.0.1 of SIL Engine.


Step-by-step guide

Our old configuration used to memorize the configuration value (CFG_VALUE), the default configuration value (CFG_DEFAULT_VALUE), the long configuration value (CFG_L_VALUE), and the default long configuration value (CFG_L_DEFAULT_VALUE). In case that the first two columns are null and the other not, we need to set the first ones to a non-null (but still empty) value.

All you need to do is set the null values to a space before upgrading.

  1. Execute the next SQL:

    UPDATE "KPLUGINSCFG"
SET CFG_VALUE = ' ', CFG_DEFAULT_VALUE = ' '
WHERE CFG_L_VALUE is not null
  2. Now you can safely upgrade to katl-commons 4.0.X.
  • No labels