Enterprise Architecture & Integration, SOA, ESB, Web Services & Cloud Integration

Enterprise Architecture & Integration, SOA, ESB, Web Services & Cloud Integration

Monday 17 September 2012

Oracle Business Rules error - Fact not found in the rule engine working memory, rule session execution failed

Recently, I got stuck with the a problem while I was learning Oracle Business Rules. Many of you would have faced this very same issue.

Fact not found in the rule engine working memory, rule session execution failed.
The rule session 60015 failed because an instance of the fact com.oracle.xmlns.rules.insuranceeligibility.ApplicantOutput could not be found in the working memory of the rule session.
This is most likely a rule modeling error. The decision service interaction expects the fact instance to exist in the working memory of the rule session. Check the rule actions in rule designer and make sure that a fact of the expected type is being asserted. If the error persists, contact Oracle Support Services. 60015


I am not intending to create a OBR tutorial page as there several good websites/blogs already available. Herewith I am including only the necessary details.

Please refer to the ruleset which I have created in JDeveloper editor.






There could be several reasons why you got this error. After hours of investigation, I 'accidentally' found the root cause - I have not defined 'else' condition in my rule set. Please find below the modified ruleset.









After the rule modification, now every thing seems to be working fine. Hope this tip will be useful in saving your valuable time. Here is the full BPEL flow for your reference.



1 comment:

  1. It will give you the same error if you pass 3000 in input.

    ReplyDelete