This information is relevant to users running secondary databases on JADE 6.3.12 and later, including all 7.0 releases.
A issue has been identified where a secondary database does not correctly replay a failed database file compact operation.
The issue can potential cause any attached secondary databases to become unusable and require re-cloning.
Hot-fixes 6.3.12.020 and 7.0.09.023 have been produced to address this and we recommend that any SDS systems upgrade to these as soon as possible.
Details of Issue
After a primary database is abnormally terminated while an outstanding file compact operation is pending, it is possible that any attached secondary database will be unable to replay the compact operation.
The fix ensures that when a a secondary replays a compact if it detects a database restart while processing a compact then the compact is skipped.
Although this is not considered a common scenario, if it did occur any affected secondary databases would need to be re-cloned.
If you have any further questions then please contact JADE Support