How to detect when defragmentation of the table associated with class System-Locks takes too long (PEGA0056 alert)

A PEGA0056 alert occurs when the defragmentation of the table associated with class System-Locks exceeds the configured time threshold. The alert helps you to monitor the performance of the defragmentation. Since the class System-Locks contains information about locks, an increase in the time taken for defragmentation results in an increase in the time taken by a requestor to acquire a lock.

Alert log message

The alert log message indicates that the defragmentation of the table associated with class System-Locks class exceeded the configured time threshold in milliseconds, as shown in the following example:

Defragmentation of Sys Locks table took more than alert threshold of 5000 ms: 5500 ms

Operation time threshold

The threshold is established in the following prconfig.xml setting:

<env name="alerts/database/syslockstimethreshold" value="5000" />

What to do

When the alert is triggered, you can do the following:

• Modify the defragmentation interval by updating the applicable Dynamic System Settings instance:

  • syslocks/defragIntervalType: Change its value to "HOURLY" or "DAILY", based on your requirement.

  • syslocks/defragIntervalInHours: Increase its value if the value of syslocks/defragIntervalType is "HOURLY".
  • syslocks/defragHourOfDay: If the value of syslocks/defragIntervalType is "HOURLY", change the hour of execution to allow defragmentation when there is minimum load on the server.

• Disable defragmentation of the table associated with class System-Locks by setting the syslocks/defragEnabled Dynamic System Settings instance to "false".

	alert log, prconfig.xml file
	Understanding alerts

SysAdmin category

Open topic with navigation