orphaned em_connector_instance_value records are included in update sets, even though parent em_connector_instance records have been excluded (since PRB680006 needed to remove the update synch attribute in Istanbul)Descriptionorphaned event management connector instance value [em_connector_instance_value] records are included in update sets, even though parent connector instance [em_connector_instance] records have had to be excluded since PRB680006 needed to remove the update synch attribute in Istanbul.If connector instance records need to be excluded, then so should connector instance value records. The em_connector_instance table was originally shipped with 'update_synch' attribute but later it was removed in 2016 via PRB680006. The reason em_connector_instance records cannot be tracked in Update Sets is that there are few fields in em_connector_instance record like - 'Event collection last run time', 'Last event collection signature', 'Last event collection status' etc. - which gets updated every time event/metric collection execute. Having 'update_synch' attribute on em_connector_instance table will add new record in [sys_update_version] table every time it runs the event/metric collection and usually this run time is every 2 min. This will cause 'sys_update_version' table grow huge and eventually it will impact the performance. This can result in days long instance upgrade times due to query performance of the sys_update_version table. Steps to Reproduce Create an Update Set, and set it currentCreate a em_connector_instance record, with em_connector_instance_value child records.Actual behaviour:The em_connector_instance_value records are captured in sys_update_cml and the update set, but the parent em_connector_instance record is not.Expected behaviour:Given that the em_connector_instance record cannot be captured in update sets/version records, the child em_connector_instance_value records should also not be.WorkaroundThis 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. The workaround is to use the Export XML and then Import XML functions to move these records between instances.Related Problem: PRB1664508