Siebel Gateway Server is Down in Production After Network Outage (Doc ID 2242469.1)

Last updated on NOVEMBER 13, 2019

Applies to:

Symptoms

Siebel Gateway server is down in production environment after network outage and Database outage.

There was a network outage which caused downtime for database. After re-started database, able to connect sqlplus but siebel is failing to start/ ODBC connection is also failing. 

From Namesrvr.log

GenericLog GenericError 1 00000008588de1c4:0 2017-01-28 16:30:30 (secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: (secmgr.cpp: 2679) error code = 4597538, system error = 0, msg1 = data source connect string or table owner is empty., msg2 = (null), msg3 = (null), msg4 = (null)

GenericLog GenericError 1 00000008588de1c4:0 2017-01-28 16:30:30 (secmgr.cpp (2751) err=4597521 sys=0) SBL-SEC-10001: (secmgr.cpp: 2751) error code = 4597521, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)

GenericLog GenericError 1 00000008588de1c4:0 2017-01-28 16:30:30 (client.cpp (309) err=4597521 sys=0) SBL-SEC-10001: (client.cpp: 309) error code = 4597521, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)

SisnTcpIp SisnSockError 1 00000008588de1c4:0 2017-01-28 16:30:30 61944: [TCPIP-server] recv() failed for sd=-1 (err=10038 | )

SisnTcpIp SisnSockError 1 00000008588de1c4:0 2017-01-28 16:30:30 61944: [TCPIP-server] send() failed for sd=-1 (err=10038 | )

SRProc.log

ServerLog LstnObjInherit 3 0000953b58831a74:0 2017-01-21 16:30:45 Inherited listening object for port 49169

ServerLog LstnObjPrivCreate 3 0000953e58831a74:0 2017-01-21 16:30:45 Created port 49173 for Server Request Broker

GenericLog GenericError 1 0000b86d58831a74:0 2017-01-28 16:00:20 NSS - ErrCode 4597521 SysErr 0

NameServerLayerLog Error 1 0000b86d58831a74:0 2017-01-28 16:00:20 Unable to read the gateway server backing file <gateway>.

Also while trying to open siebns.dat

2015-08-11T22:44:18.223Z| vcpu-0| I120: Guest: toolbox-dnd: Version: build-1283433

2015-08-11T22:44:18.223Z| vcpu-0| I120: GuestRpc: Channel 4, conflict: guest application toolbox-dnd tried to register, but it is still registered on channel 2
2015-08-11T22:44:18.223Z| vcpu-0| I120: GuestRpc: Channel 4 reinitialized.
2015-08-11T22:44:18.223Z| vcpu-0| I120: GuestRpc: Channel 4 reinitialized.
2015-08-11T22:44:18.224Z| vcpu-0| I120: GuestRpc: Channel 4 reinitialized.

Changes

Cause

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