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).
...
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
All you need to do is set the null values to an empty string (or a space , just to be sure). before upgrading.
Execute the next SQL:
Code Block UPDATE "KPLUGINSCFG" SET CFG_VALUE = ' ', CFG_DEFAULT_VALUE = ' ' WHERE CFG_L_VALUE is not null
- Now you can safely upgrade to katl-commons 4.0.0x.
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Page Properties | ||
|---|---|---|
| ||
|