My Oracle Support Banner

More Than 10,000 Rows Are Retrieved By Query That Is Fired During Logoff After Timeout (Doc ID 2504187.1)

Last updated on DECEMBER 02, 2019

Applies to:

Siebel CRM - Version 15.18 [IP2015] and later
Information in this document applies to any platform.

Symptoms

On :  15.18 [IP2015] version, System Admin

ACTUAL BEHAVIOR  
---------------
Customer has identified a non-expected query being executed that is not following DSMaxFetchArraySize=0, and is retrieving more than 10,000 rows.
The query is run after a session timeout that leads to an Undo Query.
Based on the 8.1.1.9 log file, the query was being executed, but it was not affecting the environment as the query did not go beyond 10,000 rows, and the session would have their objects destructed anyway.
Hence on 8.1.1.9, it was silently causing some performance impact, but now on 15.18 it is leading to memory exhaustion due to excessive number of rows being retrieved and memory limit being reached.


EXPECTED BEHAVIOR
-----------------------
The object manager should not run a query that may lead to excessive number of rows being retrieved


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Login to the custom eSales application (Standard Interactivity)
2) Click on My Sales Orders
3) Leave the session timeout
4) The unexpected query is fired upon timeout

Changes

 Siebel upgrade from 8.1.1.9 to 15.18

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.