Monitoring script(s) invoking srvrmgr too frequently make the Gateway Server unavailable causing Siebel Servers not to start any more (8.1.1 and above) (Doc ID 1175584.1)

Last updated on JUNE 19, 2016

Applies to:

Siebel Call Center - Version 8.1.1.2 SIA[21215] and later
Information in this document applies to any platform.
Special Instructions:
***Checked for relevance on 06-JAN-2015***
***Checked for relevance on 20-JUN-2016***

Symptoms

Siebel Servers suddenly did not start any more, even though there was no change in the Siebel environment.

SiebSrvr_28.log

immediately after benign errors like

SBL-SCC-00025: No value found in the Gateway. Default value in the repository is used.

(which means the Gateway Server can be contacted successfully, but the parameter requested is not set, so its default is used)

there were

SBL-GEN-05009: Unable to connect to the gateway server.

like

NameServerLayerLog Error 1 000024ec4c494b91:0 2010-07-23 08:26:43 Unable to connect to the gateway server.
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 NSC - ErrCode 5009 SysErr 0
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 (listener.cpp (184) err=5009 sys=0) SBL-GEN-05009: Unable to connect to the gateway server.
GenericLog GenericError 1 000024ec4c494b91:0 2010-07-23 08:26:43 (lstnsvc.cpp (150) err=5009 sys=0) SBL-GEN-05009: Unable to connect to the gateway server.

while the Gateway was still running,
and netstat output confirmed it was listening on its configured port (default: 2320)

Cause

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