My Oracle Support Banner

SCBroker Component Termination/Crash Leads to Siebel Application Object Manager Crashes - Gateway Registry read failed (Doc ID 2862250.1)

Last updated on AUGUST 19, 2022

Applies to:

Siebel CRM - Version 22.1 to 22.3 [Release V17]
Information in this document applies to any platform.



SCBroker Component is crashing and the following callstack information is found:

Called from:
/siebel/ses/siebsrvr/lib/ const&, SSstring&)+0x9a)[0xf7050aca]
/siebel/ses/siebsrvr/lib/*, int, char16_t const*)+0x499)[0xf75fb879]
/siebel/ses/siebsrvr/lib/*, int, char16_t const*)+0x2b)[0xf75fee4b]
/siebel/ses/siebsrvr/lib/,int, int)+0x539)[0xf5d08d59]
/siebel/ses/siebsrvr/lib/,unsigned int)+0x26c)[0xf5d0980c]

In the corresponding SCBroker log file, located under siebsrvr/enterprises/<enterprise_name>/<siebel_server_name>/log directory, the following error can be observed:

 It is necessary to restart the Siebel Server to recover from this behavior.


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

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