Resolving a Problem That Fails to Load Parent Rows

If Siebel CRM displays a Failed to Load Parent Rows error message, then it might be due to the presence of rows in the S_ESCL_REQ, S_ESCL_STATE table and the S_ESCL_ACTN_REQ table that reference an expired Workflow Policy. This topic describes how to use SQL queries to determine if rows exist in these tables that reference a policy that no longer exists in the S_ESCL_RULE table.

To resolve a problem that fails to load parent rows

1. Look for the following error message in the WorkMon_file_number.log trace file:

   [DBG33] 2000-01-24 08:49:30 Message: Rule not found
   [DBG33] 2000-01-24 08:49:30 Message: Failed to load parent rows

   Siebel CRM logs this error message if Workflow Monitor agent attempts to process records from the S_ESCL_REQ, S_ESCL_STATE table or the S_ESCL_ACTN_REQ table but the Workflow Policy that it is trying to review is expired or deleted.

2. To determine if records exist that reference an expired Workflow Policy, run the following query:

   select row_id, name, expire_dt from s_escl_rule
   where expire_dt is not null and expire_dt <= getdate() 

   Sysdate is an Oracle date time function. The corresponding function for SQL Server is getdate.

3. Note the ROW_ID for the expired Workflow Policy identified in step 2.

4. To determine the number of records that exist in the S_ESCL_REQ table that reference an expired Workflow Policy, run the following query:

   select * from s_escl_req where rule_id in (select row_id from s_escl_rule 
   where expire_dt is not null and expire_dt <= getdate())
   

5. Repeat the last step for the S_ESCL_STATE and S_ESCL_ACTN_REQ tables.

6. If records exist in the S_ESCL_REQ, S_ESCL_STATE table, or the S_ESCL_ACTN_REQ table that reference an expired Workflow Policy, then log in to the Siebel client and start the Workflow Monitor Agent with Ignore Errors set to TRUE.

   Workflow Monitor Agent can bypass the error and clean the S_ESCL_REQ table.

   Caution: To clean up the tables, you can temporarily set Ignore Errors to True. It is strongly recommended that you do not permanently set Ignore Errors to True.

7. Stop the Siebel Server task.

8. Restart the Siebel Server task with Ignore Errors set to FALSE.

   This step makes sure you do not overlook other types of errors.

9. If the errors continue, then delete rows by RULE_ID, expire old Workflow Policies, and delete database triggers.