EAI Siebel Adapter QueryPage leaves active cursor. (Doc ID 743116.1)

Last updated on AUGUST 16, 2016

Applies to:

Siebel CRM - Version 7.8.2 SIA [19213] and later
Siebel Financial Services CRM - Version 7.8.2.5 SIA [19227] and later
Information in this document applies to any platform.

Symptoms


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:


Begin: Business Service 'EAI Siebel Adapter' invoke method: 'QueryPage' at e1c56b0
IncrementNumOpenCursors: 1
DecrementNumOpenCursors: 0
IncrementNumOpenCursors: 1
IncrementNumOpenCursors: 2
DecrementNumOpenCursors: 1
IncrementNumOpenCursors: 2
DecrementNumOpenCursors: 1
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.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms