Last updated on MARCH 02, 2017

Applies to:

Symptoms

On : 8.1 [21039] version, System Admin

Can not start SIEBEL server
We could not start SIEBEL server on oapp1 because of segmentation fault error.

## oapp1
bash-3.2$ . ./siebenv.sh
bash-3.2$ cd bin/
bash-3.2$ ./stop_server all
Siebel Server "oapp1" (Enterprise "SBA_81")
already stopped at Fri Jan 23 14:26:40 2015
bash-3.2$ ./start_server all
Siebel Server "oapp1" (Enterprise "SBA_81")
./start_server[216]: 27815 Segmentation Fault(coredump)

## oapp2

bash-3.2$ . ./siebenv.sh
bash-3.2$ cd bin/
bash-3.2$ ./stop_server all
Siebel Server "oapp2" (Enterprise "SBA_81")
stopped at Fri Jan 23 14:46:33 2015
bash-3.2$ ./start_server all
Siebel Server "oapp2" (Enterprise "SBA_81")
./start_server[216]: 28817 Segmentation Fault(coredump)

ERROR
-----------------------
./start_server[216]: 28817 Segmentation Fault(coredump)





STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1> Login via telent / ssh to unix system hosting siebel application using siebel unix user.
2> cd /siebsrvr
3> bash-3.2$ . ./siebenv.sh
4> bash-3.2$ cd bin/
5> bash-3.2$ ./stop_server all
6> Siebel Server "oapp2" (Enterprise "SBA_81")
stopped at Fri Jan 23 14:46:33 2015
7> bash-3.2$ ./start_server all
Siebel Server "oapp2" (Enterprise "SBA_81")

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, application server services can't be started.

Cause