#2 Online Deployment and Exclusive Collection Properties

[Jade Support]

Applies to native SDS and RPS secondary systems.

This issue is relevant to the online deployment that makes changes to a schema that remove exclusive collection properties. The symptoms, should they manifest, have a relatively low impact on non SDS environments. However the impact on SDS secondary systems is severe due to the need to reclone.

Description:
If the current (pre-deployment) version of the application directly or indirectly (through inverse maintenance) adds entries to the collections that have been removed in the latest schema version, any new collection blocks created during the dual-update phase are erroneously propagated to the reorg output files. Since the collection header objects for the removed properties are correctly dropped these collection blocks become orphaned. These orphans will be detected and reported by either a logical certification or Jade Database Utility physical certification of the affected files.

SDS Impact:
The SDS secondary database replay logic correctly drops both collection headers and blocks. The affected files, although correct on the secondary, are no longer structurally compatible with their primary counterparts. The journalled audit records that describe updates to an affected file from the primary database cannot be applied to its secondary counterpart resulting in an SDS tracker halt that cannot be continued. If this issue manifests, it will be necessary to reclone the secondary from a post-deployment primary database backup.

Action:
If you know or suspect this issue may have occurred, arrange to perform a logical certification of the system. The logical certifier in current releases will generate a FIX script to remove the orphan blocks. This fix when applied to a primary database will be replayed by associated secondary databases.

Temporary Workaround:
If you intend to deploy a schema that removes exclusive collection properties, initiate the reorg with updates disallowed (i.e. offline reorg).

Product Resolution:
This issue is addressed by hot fixes 6.1.13.008 and 6.2.14.029. The fix will be included in the 6.1.14, 6.2.15 and 6.3 releases.