Memory Leak In Siebel Operation Query Step In Case No Record Found
Last updated on MARCH 02, 2017
Applies to:Siebel Loyalty Engine - Version 184.108.40.206 SIA  and later
Information in this document applies to any platform.
We have a memory leak in one of our processes, but for simplicity we have created two workflows for testing:
1. Based on LOY Member BusObj with one step Query LOY Member (by SSN)
2. Not based on any BusObj. cycling 100 000 times executing 1st WF.
By providing SSN that exists in Siebel the workflows run very well, but if I provide the SSN which does not exists in Siebel - here comes the memory leak.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms