Siebel SQLs/Error Messages >  SBL-ESC-00053: Error loading rule definitions

SBL-ESC-00053: Error loading rule definitions

APPLIES TO:

Siebel Workflow - Version 7.8.2 SIA [19213] and later
Information in this document applies to any platform.
Error Message Area: Escalation Agent
Checked for Relevance as on 20-May-2013

PURPOSE
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-ESC-00053: Error loading rule definitions from Workflow Monitor Agent (WorkMon) component task.

SCOPE
This document is informational and intended for any user.

DETAILS
Explanation
An error was encountered while WorkMon is reading the workflow policy definitions from the database. It is likely that the value provided for the Group Name parameter for the WorkMon task is incorrect or is an inactive Workflow Policy Group.

Corrective Action
Make sure the Workflow Policy Group is active, and that the name is correctly specified for the Workflow Monitor Agent component task in the Group Name parameter. If the failure appears to be related to recent customization of Workflow Policy Objects in the repository, then choose Validate on the object in Siebel Tools > Workflow Policy Object to validate that the modified objects are configured correctly.

WorkFlow Policy Problems ( SBL-ESC-00053)

APPLIES TO:
Siebel CRM - Version 8.0.0.13 [20448] and later
Information in this document applies to any platform.
SYMPTOMS
I create a new workflow policy object based in a new table named CX_IB_REG_ACT which is a custom table.
I create a custom Workflow Monitor Agent component WorkMonSV.
When I start the Work Monitor Agent task, i.e., WorkMonSV task, it fails with the error SBL-ESC-00053: Error loading rule definitions:

2021 2013-09-13 16:41:07 2013-09-13 16:41:49 -0500 000007a3 001 ffff 0001 09 WorkMonSV 11534339 2740 8032 D:\sba80\siebsrvr\log\WorkMonSV_0011_11534339.log 8.0.0.13 [20448] ESN

SQLSlowQuery Statement 4 0000000452330ab4:0 2013-09-13 16:41:26

select link.ROW_ID, link.SRC_TBL_ID, link.SRC_COL_ID,
link.TAR_TBL_INST_ID, link.TAR_COL_ID, link.PRIMARY_FLG,
link.NAME, link.ADDTL_JOIN_SPEC
from SIEBEL.S_ESCL_LINK link,
SIEBEL.S_ESCL_OBJECT obj
where obj.NAME = ? and
obj.REPOSITORY_ID = ? and
(obj.INACTIVE_FLG = 'N' or obj.INACTIVE_FLG IS NULL) and
link.OBJECT_ID = obj.ROW_ID and
(link.INACTIVE_FLG = 'N' or link.INACTIVE_FLG IS NULL)

SQLSlowQuery Bind Variables 4 0000000452330ab4:0 2013-09-13 16:41:26 01:IBP Reg Action IVR
02:1-1-1

ProcReq GenericFatal 0 0000000452330ab4:0 2013-09-13 16:41:26 IBP Reg Action IVR in Load

GenericLog GenericError 1 0000000452330ab4:0 2013-09-13 16:41:26 Message: ESCL-07,
Additional Message: IBP Reg Action IVR

ProcReq GenericFatal 0 0000000452330ab4:0 2013-09-13 16:41:26 Object Info in LoadRules

GenericLog GenericError 1 0000000452330ab4:0 2013-09-13 16:41:26 Message: GEN-11,
Additional Message: Object Info

ProcReq GenericFatal 0 0000000452330ab4:0 2013-09-13 16:41:26 Error in LoadRules

GenericLog GenericError 1 0000000452330ab4:0 2013-09-13 16:41:26 Message: ESCL-16,
Additional Message: Error

ProcReq GenericFatal 0 0000000452330ab4:0 2013-09-13 16:41:26 Creacion de Actividad Siebel IVR in LoadRules

GenericLog GenericError 1 0000000452330ab4:0 2013-09-13 16:41:26 Message: ESCL-27,
Additional Message: Creacion de Actividad Siebel IVR in LoadRules

SQLSummary Stmt 4 0000000452330ab4:0 2013-09-13 16:41:26

select rle.NAME, rle.OBJECT_NAME, rle.ROW_ID,
rle.RULE_DURATION, rle.QUALIFY_COUNT, rle.SUB_TYPE_CD, rle.ASGN_OBJECT_NAME,
rle.ACTIVATE_DT, rle.EXPIRE_DT, {fn ifnull (rle.BATCH_FLG, 'N')}
from SIEBEL.S_ESCL_RULE rle,
SIEBEL.S_ESCL_GROUP grp
where grp.NAME = ? and
rle.GROUP_ID = grp.ROW_ID

SQLSummary BindVar 4 0000000452330ab4:0 2013-09-13 16:41:26 01:IBPRegActSiebelIVR

GenericLog GenericError 1 0000000452330ab4:0 2013-09-13 16:41:26 (smishell.cpp (342) err=458805 sys=0) SBL-ESC-00053: Error al cargar definiciones de regla

CAUSE
The log shows it failed in loading the new Workflow Policy Object 'IBP Reg Action IVR' which is based on the new table CX_IB_REG_ACT.

The new table schema in Siebel Repository is not synchronized to the Siebel database.
The diccache.dat is not refreshed for the new table.

SOLUTION
The issue is resolved by doing the following:

1. Make sure the table and workflow policy object exist in the Siebel database the WorkMonSV task is started on, not from the SRF file.

They should be seen in Siebel Tools > Table and Siebel Tools > Workflow Policy Object connecting for Siebel Repository connecting to Siebel data source.

When WorkMonSV task is starting up, it first loads the workflow configurations and rules from Siebel Repository connecting to Siebel database.
If any of the configurations are missing/invalid then the task will fail. If you use local database for the development, you need to check the project back in to ensure the new Workflow Policy Object details are placed in the repository in the server database.

2. Make sure the custom table CX_IB_REG_ACT in Siebel Tools is sync up with the Siebel database.

In the database, make sure the table columns in Siebel Tools > Table > Column match the table columns in the Siebel database.

In Siebel database, you can look at table columns by using the database command. For example, Oracle database is: Describe CX_IB_REG_ACT, MS SQL Server is exec sp_columns CX_IB_REG_ACT.

3. After you sync up the table with Siebel database, the diccache.dat file in siebsrvr\bin folder should be recreated for including the table definition.

If the diccache.dat has an old timestamp, which means the new table definition is not loaded, then you can recreate diccache.dat by renaming it first and restart Siebel Server service.

When Siebel Server startup does not find the diccache.dat file, it will recreate it.