Maximum Cursor Size Nor Prefetch Size Properties Did Not Prevent Large Update
(Doc ID 2558209.1)
Last updated on NOVEMBER 06, 2019
Applies to:Siebel Financial Services CRM - Version 184.108.40.206.11 [IP2013] and later
Information in this document applies to any platform.
There was a custom view for a user to edit a custom column on S_ORDER. The business component on this view has a max cursor size property at 2,000 and a Prefetch size property at 500. A user was able to update 15 million records from this view even though these properties were set on the business component. The Select All and Change Records options on the Applet menu were used to do this. This can froze the Siebel session and the updates continued for 14 hours.
The SQL updates looked like this in the database:
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