| Siebel Administration > One or more Siebel servers would not start
There can be several situations where Siebel server might not start.
In one case we had these error messages in the Object Manager files
ServerLog ProcessExit 1 000034215050166a:0 2012-09-12 15:53:15 SCBroker 5796 SBL-GEN-00001 Process 5796 exited with error -
GenericLog GenericError 1 000034215050166a:0 2012-09-12 15:53:15 (schedule.cpp (995) err=1376352 sys=0) SBL-SMI-00096: The maximum number of restarts (10) for MinUpTime has been reached. The component SCBroker will not be restarted again.
NotifyEvt NotifyErrors 1 000034215050166a:0 2012-09-12 15:53:15 SBL-ADM-09152Could not send a notification message because we could not connect to the notification pipe (SIEBEL_SERVER_NAME), retCode = (9603), nSysErr = (0)
ServerLog ProcessCreate 1 000034205050166a:0 2012-09-12 15:53:15 Created server process (OS pid = 5798 ) for SCBroker
ServerLog ProcessCreate 1 000034205050166a:0 2012-09-12 15:53:15 Created server process (OS pid = 5799 ) for SCBroker
ServerLog ProcessExit 1 000034215050166a:0 2012-09-12 15:53:15 SCBroker 5797 SBL-SVR-09127 Process 5797 exited with error - Internal: Fail to initialize the shared memory resource for the process.
GenericLog GenericError 1 000034215050166a:0 2012-09-12 15:53:15 (schedule.cpp (995) err=1376352 sys=0) SBL-SMI-00096: The maximum number of restarts (10) for MinUpTime has been reached. The component SCBroker will not be restarted again.
NotifyEvt NotifyErrors 1 000034215050166a:0 2012-09-12 15:53:15 SBL-ADM-09152Could not send a notification message because we could not connect to the notification pipe (SIEBEL_SERVER_NAME), retCode = (9603), nSysErr = (0)
ServerLog ProcessExit 1 000034215050166a:0 2012-09-12 15:53:15 SCBroker 5798 SBL-SVR-09127 Process 5798 exited with error - Internal: Fail to initialize the shared memory resource for the process.7
You might also get this error message separately or on its own (with different error messages in the Object Manager File)
(Error: No remembered search string)
Solution: We need to clean up the Siebel Server Execution Environment.
Remember never run these if Siebel server is running. Check first using the prstat command and checking if any siebel processes are running.
Load siebel environment variables - load the variables in siebenv.sh file.
Stop all Siebel Servers using the stop server all command.
reset_server -e SIEBEL_ENTERPRISE_NAME
siebclean -f $SIEBEL_ROOT/admin/SIEBEL_ENTERPRISE_NAME.SIEBEL_SERVER_NAME.shm -q - cleaning the shared memory
cleansync -f $SIEBEL_ROOT/sys/osdf.SIEBEL_ENTERPRISE_NAME.SIEBEL_SERVER_NAME -d
siebctl - r $SIEBEL_ROOT -S siebsrvr -i SIEBEL_ENTERPRISE_NAME.SIEBEL_SERVER_NAME -k -q
mwcleanup -s -k > /dev/null - cleaning the MainWin structures
After this start the Siebel Server(s) using the start_server all command.
If these steps above do not work, try following these steps
ps -ef |grep <siebel_owner> - check the running siebel processes and kill all of them
ps -ef |grep siebsvc - check the running siebel service and kill it
ipcs -ms -p - check the blocking PIDs (running on the siebel server owher) that block shared memory and/or semaphores and that are candidates to be killed
ipcrm -m <shared_memory_segment_ID> - use this command to remove the shared memory structures found by the ipcs command above
ipcrm -m <semaphore_ID> - use this command to remove the semaphores found by the ipcs command above
rm /tmp/MW* - remowe the Mainwin files
rm $SIEBEL_ROOT/sys/osdf* - remowe the Mainwin files
rm $SIEBEL_ROOT/admin/*.shm - remowe the shared memory files
After this start the Siebel Server(s) using the start_server all command.
The error message - (Error: No remembered search string) might need a different solution. It has been described here -
http://www.eir.me/siebel.php?art_id=104&cat=1
| 
