Clone Excludes/Preservers are missing for SNMP Trap and vCenter Event based Discovery MID Server extension contexts (ecc_agent_ext_context_trap / ecc_agent_ext_context_vcenter) - Known Error

Clone Excludes/Preservers are missing for SNMP Trap and vCenter Event based Discovery MID Server extension contexts (ecc_agent_ext_context_trap / ecc_agent_ext_context_vcenter) Description Clone Excludes/Preservers are missing for SNMP Trap and vCenter Event based Discovery MID Server extension contexts (ecc_agent_ext_context_trap / ecc_agent_ext_context_vcenter). After a clone, on the clone target instance, this causes ghost/orphan records in the ecc_agent_ext_context table for these class of record, that when opened give a "Record not found" error.

Event Management customers use the SNMP Trap collector [ecc_agent_ext_context_trap] to listen for SNMP traps. Event Management and Cloud Discovery uses the VMware vCenter Server (vCenter) connector [ecc_agent_ext_context_vcenter] to receive events from your VMware vSphere environment.

Steps to Reproduce

Install Event Management and Discovery on a pair of instances, to use as a clone source and target Install a MID Server on the target On the clone target instance, set up a SNMP Trap collector [ecc_agent_ext_context_trap] and VMware vCenter Server (vCenter) connector [ecc_agent_ext_context_vcenter]. Clone the source over the target. The ecc_agent_ext_context_trap and ecc_agent_ext_context_vcenter records will now be corrupted, that when opened from the ecc_agent_ext_context list, gives a "Record not found" error, and the listeners will not be able to be started. Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.

Repair:

To repair bad records, please use this KB article: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0716609

To find the records, set the script up with: findOrphans('ecc_agent_ext_context', null, false);

Then to delete them use: findOrphans('ecc_agent_ext_context', null, false);

You may then need to set up the MID Server extensions/collectors/listeners again.

Prevention:

To prevent this in future, you will need to add Clone excludes and preservers for ecc_agent_ext_context and all the tables that extend it.

You can see a list of what child tables you have in your instance using this list filter: https:// .service-now.com/sys_db_object_list.do?sysparm_query=super_class.label%3DMID%20Server%20Extension%20Context%5EORsuper_class.super_class.label%3DMID%20Server%20Extension%20Context&sysparm_first_row=1&sysparm_view=