In existing JADE systems that have been upgraded to JADE 2018 and that contain string large objects (slobs) or binary large objects (blobs) that meet some very specific boundary conditions, and have then been deleted, free space corruption may eventuate. This may lead to data corruption.
In existing JADE systems that have been upgraded to JADE 2018 and that contain data meeting some very specific boundary conditions, data in database blocks may be misaligned or in a worst-case scenario, overwritten.
To ensure that this does not occur, please install JADE 2018 hot fix #23 as soon ...
Upgrades from 7.1 to JADE 2016 Service Pack 1 (SP1 - 16.0.02) can cause an issue with existing Skins in user schemas. For the issue to occur, a user Skin must define either a JadeSkinListBox or JadeSkinTable entity.
Systems upgraded from 7.1 to the initial release of JADE 2016 (16.0.01), then ...
In JADE 7.1.09 and JADE 2016 Service Pack 1, the Meta Certifier now supports the option of running multiple workers. In JADE 7.1.09 only, when a Meta Certify operation is performed using multiple workers, some fixes generated by the worker processes may not be added into the consolidated _logcert ...
The issue you have encountered is due to the increase in Class Numbers in JADE 7.1, which have been extended to over 1000000, this has increased the maximum size of Object Identifiers from 16 in JADE 7.0 to 28 in JADE 7.1. The OID Mapping Option "Map To String" did not contain sufficient ...