How to Reset Siebel Server and clean all files ?

The advice on clearing .shm and .osdf is generically good, however does sometimes fail and then it is important to consider deleting and recreating the siebsrvr/sys/svc* (Siebel service) and recreate with siebctl command. You may have to kill some other process as well.
The full clean up solution as documented by Siebel is provided below for completeness:

In order to fix this behavior and guarantee you have a clean environment, please do the following:

1. Shutdown the Siebel Server and run the following commands to clean all structures that may remain:

% stop_server ALL
% reset_server -e <enterprise_name> <server_name>
% siebclean -f $SIEBEL_ROOT/siebsrvr/admin/<enterprise_name>.<server_name>.shm -q
% cleansync -f $SIEBEL_ROOT/siebsrvr/sys/osdf.<enterprise_name>.<server_name> -d
% siebctl -r $SIEBEL_ROOT -S siebsrvr -i <enterprise_name>:<server_name> -k -q
% mwcleanup -silent 2>/dev/null

2. If using AIX, log into UNIX as root and run the following command:

% /usr/sbin/slibclean

3. Ensure no Siebel processes are running and check that there are no semaphores or shared memory segments allocated for the UNIX user who owns the Siebel Server installation:

% ps -ef | grep <username>
% ipcs -b

4. If there are any processes, shared memory segments or semaphores stuck in memory, they can be killed by using the following commands, respectively:

% kill -9 <process_ID>
% ipcrm -m <shared_memory_segment_ID>
% ipcrm -s <semaphore_ID>

5. Remove the following files if they still exist:

$SIEBEL_ROOT/siebsrvr/sys/osdf.<enterprise_name>.<server_name>
$SIEBEL_ROOT/siebsrvr/admin/<enterprise_name>.<server_name>.shm

6. Remove all svc* files or move all of them out from $SIEBEL_ROOT/siebsrvr/sys directory.

7. Recreate the correct svc* file:

% siebctl -S siebsrvr -i "<enterprise_name>:<server_name>" -a -g "-g <gateway_name> -e <enterprise_name> -s <server_name> -u SADMIN" -e SADMIN

8. Restart the Siebel Server:

% start_server all

One should note that if there are still any processes, semaphores or shared memory segments stuck in memory, the machine will need to be rebooted before recreating the svc* file (between steps 6 and 7).

Customers should also note that recreating the svc* file (steps 6 and 7) is not necessary in all situations, and in most cases step 1 only is sufficient to guarantee a clean startup.

[su_divider]

@skmeSiebel