Siebel Workflow Records Stuck in S_ESCL_REQ.
GoalRecords are not picked up from the S_ESCL_REQ table after the policy violations. Customer has defined a Workflow Policy Program with custom SQL as a policy action.
Solution
When Workflow Policy Programs are defined as actions for any Workflow Policies, care must be taken to make sure any custom SQL added in the Policy Programs have all the column lengths with-in acceptable range, typically 30 characters (depends on the ODBC connection as well), and if it exceeds that, customers need to put aliases in place for those columns. Ignoring that would to a situation where all violated policies remain in the E_ESCL_REQ table.
Typical error noticed in the Workflow Monitor Agent log files when this issue happens:
ProcReq GenericFatal 0 000000024d7e0948:0 2011-03-14 23:50:24 Column Name Length exceeded max limit in OutputBindColumns
GenericLog GenericError 1 000000024d7e0948:0 2011-03-14 23:50:24 Message: ESCL-19,
Additional Message: Column Name Length exceeded max limit
Making sure that all columns in the custom SQL are of appropriate length will resolve this issue and the records will be picked up properly from the S_ESCL_REQ table.
No comments :