How To Implement Large Scale Batch Processing - SRProc Performance?
(Doc ID 2470697.1)
Last updated on NOVEMBER 18, 2019
Applies to:Siebel CRM - Version 7.5.1 SIA  and later
Information in this document applies to any platform.
We have Siebel Enterprise with a lot of business process, including async Workflow Processes, Repeating Job and etc.
In log-file of component Siebel SRProcessor we can to see SQL Select-statement, which selected all Jobs or another tasks.
In our case - it is more than 450 values in Select Statement ("201803_SRProcessor_SQL.txt" attachment), and count of this values increasing with develop new business processes (attachment 201810_SRProcessor_SQL.txt).
A] What is the impact on SRPRoc work when SQL-statement contains more than 1000 values in section "IN" (SQL Limitation)?
IN srProc log we see below SQL:
From SIEBEL.S_SRM_REQUEST R, SIEBEL.S_SRM_ACTION A, SIEBEL.S_USER U
where STATUS = 'QUEUED' AND .....
and A.NAME in ( ............ < over 1000 comps > )
B] How to implement large scale batch processing without impacting SRProc performance?
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