VERIFIED SOLUTION i
X

Resolve 'schedule event' from 'sarp_event' table not getting deleted with Sarpdel executed with '/Type=Event' in Sagent

Issue

Sagent performance degrades over a period of time with 'plan scheduling'.

Cause

This is a known defect in Sagent that while running the repository cleanup (both using Sagent admin or 'Sarpdel /Type=Event' command), the entry for 'schedule event' from 'sarp_event' does not get deleted. These entries get accumulated over a period of time causing the performance degradation.

User-added image

Although, entries for following events get deleted successfully using the 'Sarpdel /Type=Event' command:
  • Publish/ Un-publish/ Subscribe/ Un-sucribe the plan
  • Edit the flow of any published plan.

Resolution

UPDATED: April 25, 2018


As a workaround, update the 'sarp_event' table using the following query:
UPDATE sarp_event SET tombstone = 1 WHERE object_name = 'Schedule Event'
Further, run the 'Sarpdel /Type=Event' command, which deletes the entry for 'Schedule Event'

Environment Details

Product Feature: SarpDel

Downloads

  • No Downloads