SBL-OSD-00001: Internal: Function call timed out (0) After Component Termination Causes System Performance Degradation
(Doc ID 2522723.1)
Last updated on NOVEMBER 23, 2022
Applies to:
Siebel CRM - Version 8.1.1.8 [23012] to 16.19 [IP2016] [Release V8 to V16]Information in this document applies to any platform.
Symptoms
Customer encountered slowness during Siebel navigation. When this behavior was encountered the error "Failure to establish connection" when navigating to Siebel Administration views.
In the Enterprise log file the SBL-OSD-00001 error is found after AsgnSrvr component termination.
It is necessary to restart the Siebel Server to recover.
ERRORS
ServerLog ProcessExit 1 0000278e5c7d5e9e:0 2019-03-14 11:32:42 AsgnSrvr 5050 TERMINATED Process 5050 was terminated
ServerLog ProcessCreate 1 0000278c5c7d5e9e:0 2019-03-14 11:33:15 Created server process (OS pid = 14472 ) for ServerMgr
ServerLog ProcessExit 1 0000278e5c7d5e9e:0 2019-03-14 11:33:15 ServerMgr 14121 SBL-OSD-00001 Process 14121 exited with error - Internal: Function call timed out (%sysError)
GenericLog GenericError 1 0000278e5c7d5e9e:0 2019-03-14 11:34:15 (scfdata.cpp (1122) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)
ServerLog ProcessCreate 1 0000278c5c7d5e9e:0 2019-03-14 11:34:47 Created server process (OS pid = 15106 ) for ServerMgr
GenericLog GenericError 1 0000278e5c7d5e9e:0 2019-03-14 11:34:45 (sisobj.cpp (1288) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)
ServerLog ProcessCreate 1 0000278c5c7d5e9e:0 2019-03-14 11:35:17 Created server process (OS pid = 15218 ) for ServerMgr
ServerLog ProcessExit 1 0000278e5c7d5e9e:0 2019-03-14 11:35:15 WfProcBatchMgr 24403 SBL-OSD-02006 Process 24403 exited with error - Process exited because it received signal SIGABRT.
GenericLog GenericError 1 0000278e5c7d5e9e:0 2019-03-14 11:36:15 (scfdata.cpp (1122) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)
GenericLog GenericError 1 0000278e5c7d5e9e:0 2019-03-14 11:36:15 (sisobj.cpp (1288) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)
ServerLog ProcessExit 1 0000278e5c7d5e9e:0 2019-03-14 11:32:42 AsgnSrvr 5050 TERMINATED Process 5050 was terminated
ServerLog ProcessCreate 1 0000278c5c7d5e9e:0 2019-03-14 11:33:15 Created server process (OS pid = 14472 ) for ServerMgr
ServerLog ProcessExit 1 0000278e5c7d5e9e:0 2019-03-14 11:33:15 ServerMgr 14121 SBL-OSD-00001 Process 14121 exited with error - Internal: Function call timed out (%sysError)
GenericLog GenericError 1 0000278e5c7d5e9e:0 2019-03-14 11:34:15 (scfdata.cpp (1122) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)
ServerLog ProcessCreate 1 0000278c5c7d5e9e:0 2019-03-14 11:34:47 Created server process (OS pid = 15106 ) for ServerMgr
GenericLog GenericError 1 0000278e5c7d5e9e:0 2019-03-14 11:34:45 (sisobj.cpp (1288) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)
ServerLog ProcessCreate 1 0000278c5c7d5e9e:0 2019-03-14 11:35:17 Created server process (OS pid = 15218 ) for ServerMgr
ServerLog ProcessExit 1 0000278e5c7d5e9e:0 2019-03-14 11:35:15 WfProcBatchMgr 24403 SBL-OSD-02006 Process 24403 exited with error - Process exited because it received signal SIGABRT.
GenericLog GenericError 1 0000278e5c7d5e9e:0 2019-03-14 11:36:15 (scfdata.cpp (1122) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)
GenericLog GenericError 1 0000278e5c7d5e9e:0 2019-03-14 11:36:15 (sisobj.cpp (1288) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |