=====DuplicateSyncSchedulesCreated=====

**Level:**   __Major__    


**Purpose:** Temporary measure until https://errigal.atlassian.net/browse/OPSDEV-284 is fixed. Bug in snmp manager which is creating duplicate alarm severity syncs in network_element_sync_setting table

**Scenario:** Alarm sync has no recent successful alarm severity sync, so the snmp manager creates a new one but doesn't check if there's one there already

**Resolution:** Remove duplicate sync settings

**Manual Action Steps:** Check for duplicates
<code>
select network_element_id ,schedule_expression, job_type, count(*) 
from snmp_manager.network_element_sync_setting ness 
where sync_status != 'DISABLED'
group by network_element_id,schedule_expression, job_type
having count(*) > 1
order by count(*) desc;</code>

Remove duplicates
<code>DELETE ness1 FROM network_element_sync_setting ness1
INNER JOIN network_element_sync_setting ness2 
WHERE 
    ness1.id < ness2.id AND 
    ness1.network_element_id = ness2.network_element_id
    AND ness1.job_type = 'ALARM_SEVERITY_SYNC' AND ness2.job_type = 'ALARM_SEVERITY_SYNC'
    and ness1.schedule_expression = '2-00:00' and ness2.schedule_expression = '2-00:00';</code>



**Auto Clear:** When no sync settings have more than 20 duplicates