Mid Server Capabilities [ecc_agent_capability] table should not be excluded/preserved in clones (we only need MID Server-specific ecc_agent_capability_m2m records) - Known Error

Mid Server Capabilities [ecc_agent_capability] table should not be excluded/preserved in clones (we only need MID Server-specific ecc_agent_capability_m2m records) Description Mid Server Capabilities [ecc_agent_capability] should not be excluded/preserved in clones. There are common to all instances in the set, and not specific to any MID Server. Only the MID-Server specific ecc_agent_capability_m2m records need to be excluded and preserved.

Store apps and plugin activations can add these records. That means something installed on a clone target before a clone, and but not on the clone source, can cause a mis-match between the records and the apps/plugins installed after the clone. The clone process could in-effect add or remove a plugin/app, but the records remain from before the clone.

Although the steps to reproduce this are unconfirmed, this setting might also be causing ecc_agent_capability records to be deleted on the clone target.

Steps to Reproduce

For this example instance A is production and the clone source. Instance B is sub-production and the clone target.

In instance B, install Discovery, ACC-F, Discovery and Service Mapping Patterns, or anything that adds ecc_agent_capability record. (Don't install these on instance A.) Clone A over B Expected behaviour: The records should match what plugins are installed, as defined by the source instance. That can be guaranteed by not excluding/preserving. Actual behaviour : B now no longer has those plugins installed, so should no longer have those records, but it does because they were preserved.

You could also install plugins on A, but not B, and you will end up with ecc_agent_capability records missing for installed apps on B after the clone. By excluding, those don't get copied.

Workaround This problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this article to be notified when more information becomes available.

As a workaround, the ecc_agent_capability table can be removed from the lists on the clone source instance, for both clone exclude tables, and clone preservers. This may need doing before every clone, in case an upgrade has put those back in the meantime.