#22 JADE 7 migration and JadeBytes
Posted: Mon Dec 03, 2012 10:15 am
Overview
In the earliest implementation of JadeBytes (6.2.13 and earlier), instances were created with an incorrect internal representation. *This anomaly only becomes apparent once the system is upgraded to JADE 7.0*. When accessed in JADE 7 these instances cause anomalous behaviour (the value cannot be read and sometimes a crash ensues).
The issue is the subject of PAR 58738 and is addressed in 7.0.06 and hot fix 7.0.5.22.
If you have systems with JadeBtytes instances created in JADE 6.2.13 or earlier then please read on...
Detecting the issue
1) The issue can be detected in a system by performing a test migration\upgrade of the 6.3 system to 7.0.05 (the upgrade to this release using the install shield will not detect the issue), installing hot fix 7.0.05.22 and running a workspace that reports instances of the problem:
2) If a manual upgrade/migration to 7.0.05 is performed, and the hot fix 7.0.05.22 is used in that process, then the upgrade will not complete. The message log will log the problem objects and the system cannot be started. These behaviours will be built into the base release of 7.0.06 and above.
3) In JADE 7.0.06+ the installer automatically detects problem objects and aborts the migration. The jommsg log will indicate which objects were not created correctly.
Repairing the issue if present
Prior to migrating a system from JADE 6.3 to JADE 7.0 the data anomaly can be rectified by resetting the content, e.g.
In the earliest implementation of JadeBytes (6.2.13 and earlier), instances were created with an incorrect internal representation. *This anomaly only becomes apparent once the system is upgraded to JADE 7.0*. When accessed in JADE 7 these instances cause anomalous behaviour (the value cannot be read and sometimes a crash ensues).
The issue is the subject of PAR 58738 and is addressed in 7.0.06 and hot fix 7.0.5.22.
If you have systems with JadeBtytes instances created in JADE 6.2.13 or earlier then please read on...
Detecting the issue
1) The issue can be detected in a system by performing a test migration\upgrade of the 6.3 system to 7.0.05 (the upgrade to this release using the install shield will not detect the issue), installing hot fix 7.0.05.22 and running a workspace that reports instances of the problem:
Code: Select all
rootSchema._validateJadeBytesBlocks();3) In JADE 7.0.06+ the installer automatically detects problem objects and aborts the migration. The jommsg log will indicate which objects were not created correctly.
Repairing the issue if present
Prior to migrating a system from JADE 6.3 to JADE 7.0 the data anomaly can be rectified by resetting the content, e.g.
Code: Select all
jadeBytes.setContent(jadeBytes.getContent());