Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Performance Tuning Guide > Tuning Siebel Workflow for Performance > Monitoring Workflow Policies >
Monitoring the S_ESCL_REQ Table
Figure 3 shows the S_ESCL_REQ table.
When a trigger fires against a Workflow policy condition, a record is inserted in the Escalation Request table, S_ESCL_REQ. This table contains all the rows in the database that could trigger a Workflow Policy to take action. After the workflow Monitor Agent processes a request, it removes the row from this table.
Use your database tools to monitor the size and efficiency of the table. If the table becomes very large, this could indicate that the number of policies being monitored is too large and a new Workflow Policies process needs to be created to share the load. If rows are being monitored and not being removed after the time interval is met, this could indicate that a policy was deactivated without removing the database triggers. The triggers are continuing to send data that is not being acted on by a Workflow Policies instance.
NOTE: If you expire or delete any active Workflow Policies, confirm that no outstanding records are in the S_ESCL_REQ, S_ESCL_STATE, or S_ESCL_ACTN_REQ tables.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Performance Tuning Guide Published: 24 October 2003 |