EAI Siebel Adapter QueryPage leaves active cursor.
(Doc ID 743116.1)
Last updated on MARCH 01, 2018
Applies to:Siebel CRM - Version 7.8.2 SIA  and later
Siebel Financial Services CRM - Version 188.8.131.52 SIA  and later
Information in this document applies to any platform.
The customer is using DB2 (database version 8) on OS/390 and they have a workflow that executes the QueryPage method on the EAI Siebel Adapter. If the number of records that meet the search specification is greater than the PageSize and QueryPage is not invoked again until LastPage = true, the cursor is not closed and the thread is left active after the workflow has completed. If the number of records that meet the search specification is less than or equal to the PageSize or QueryPage is invoked again until LastPage = true, the thread is left inactive or disappears.
The following information is included in the siebel log file:
End: Business Service 'EAI Siebel Adapter' invoke method: 'QueryPage' at e1c56b0
This suggests that the number of open cursors did not return to 0.
The customer’s DB2 DBA confirmed that the active thread can be seen on the DB2 side.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document