Batch Component not being registered by SRProc although it appears as online

(Doc ID 1395591.1)

Last updated on SEPTEMBER 07, 2016

Applies to:

Siebel CRM - Version 8.1.1 [21112] and later
Siebel System Software - Version [IP2013] to [IP2013] [Release V8]
Information in this document applies to any platform.



After a Siebel service restart it was observed that SRProc requests for a certain batch component,  in our example WfProcMgr were not executed anymore.


The following symptoms could be seen:


a) Server bounce or WfProcMgr component bounce took place

b) SRProc was up and running

c) the batch component, in our example WfProcMgr,  could not be found anymore in the SRProc log file in the IN clause stating the enabled components. When the SRProc starts it will run a query to check for queued requests

For example....

... ENABLED_FLG          = 'Y' and A.NAME in  ( 'AdminNotify' , 'CommConfigMgr' , 'CommInboundProcessor' , 'CommInboundRcvr' , 'CommOutboundMgr' , 'CommSessionMgr' , 'DQMgr' , 'FSMSrvr' , 'GenTrig'  )

The "WfProcMgr" Workflow components is not included in this list and therefore were never processed.


d) although not seen in the SRPRoc log file, the WfProcMgr component showed as online in srvrmgr "list comps" command

e) Entries in S_SRM_REQUEST table for this component remain in status of QUEUED.



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