On Linux environment, Siebel Server is up but many components fail with the segmentation fault. (Doc ID 1912299.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version 8.1.1.6 [21233] and later
Linux x86-64

Symptoms

All of sudden, GenNewDB, ServerMgr and other components starts to exit with SIGSEGV error. After restarting Siebel Server, SRBroker starts to exit with SIGSEGV error as well. Also odbcsql fail with the segmentation fault.

 

1) When ServerMgr exits, the following error is recorded on Siebel Enterprise log file.

ServerLog   ProcessCreate     1     0000376f538e2dd4:0      2014-06-16 16:18:11     Created server process (OS pid =      19935 ) for ServerMgr

ServerLog   ProcessExit 1     0001dc4c538d09ea:0      2014-06-16 16:18:12     ServerMgr       19935 SBL-OSD-02011   Process 19935 exited with error - Process exited because of a segment violation (SIGSEGV)

 

2) Corresponding "T201406161618_P019935.fdr" file shows the following information.

"FdrID","UTC","ThreadID","AreaSymbol","AreaDesc","SubAreaSymbol","SubAreaDesc","UserInt1","UserInt2","UserStr1","UserStr2"

1,1402903091,1440897664,Fdr_SEC,Security / Authentication,FdrSub_SEC_LOGIN,Login to Sec. Adpt.,0,0,"SBL_SETUP_USER","Begin"

2,1402903091,1440897664,Fdr_SEC,Security / Authentication,FdrSub_SEC_INIT,Sec. Adpt. Initialization,0,0,"",""

3,1402903091,1440897664,Fdr_FDR,Fdr Internal,FdrSub_FDR_CRASH,** CRASHING THREAD **,0,0,"",""

** Neither ServerMgr*.log nor srvrmgr*.log files are generated.

 

3) After Siebel Server is restarted, Siebel Enterprise Server log shows the following error.

ServerLog ProcessCreate 1 0000377353a06ce5:0 2014-06-18 09:53:21 Created multithreaded server process (OS pid = 28323 ) for SRBroker

ServerLog ProcessExit 1 0000377453a06ce5:0 2014-06-18 09:53:21 SRBroker 28323 SBL-OSD-02011   Process 28323 exited with error - Process exited because of a segment violation (SIGSEGV)

ServerLog ProcessCreate 1 0000377353a06ce5:0 2014-06-18 09:53:26 Created multithreaded server process (OS pid = 28355 ) for SRBroker

ServerLog ProcessExit 1 0000377453a06ce5:0 2014-06-18 09:53:26 SRBroker 28355 SBL-OSD-02011   Process 28355 exited with error - Process exited because of a segment violation (SIGSEGV)

 

<SRBroker exits then restarts 10 times.>

 

ServerLog ProcessCreate 1 0000377353a06ce5:0 2014-06-18 09:54:06 Created multithreaded server process (OS pid = 28732 ) for SRBroker

ServerLog ProcessExit 1 0000377453a06ce5:0 2014-06-18 09:54:06 SRBroker 28732 SBL-OSD-02011   Process 28732 exited with error - Process exited because of a segment violation (SIGSEGV)

GenericLog GenericError 1 0000377453a06ce5:0 2014-06-18 09:54:06 (schedule.cpp (927) err=1376352 sys=0) SBL-SMI-00096: The maximum number of restarts (10) for MinUpTime has been reached. The component SRBroker will not be restarted again.

** There is no SRBroker*.log.

 

4) Based on the information from "T201406161618_P019935.fdr", odbcsql is used to see if database connection can be established. It fails as below.

$ odbcsql /u SADMIN /p SADMIN /s SBA_81_DEV3_DSN

...

Logging into "SBA_81_DEV3_DSN" as "SADMIN" ...

Segmentation fault

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