Sporadic Server Busy Error While Login Into AOM
Last updated on FEBRUARY 01, 2017
Applies to:Siebel CRM - Version 15.6 [IP2015] and later
Information in this document applies to any platform.
- Application users are getting server busy error messages
- The SiebelConnectionBroker(SCBroker) component is trying to connect to unavailable ApplicationObjectManager (AOM) PID
- Even restarting Gateway and Siebel servers the SiebelConnectionBroker(SCBroker) sometimes still pointing to OLD ApplicationObjectManager (AOM) PID which causing server busy error at client end.
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