Siebel cleanup procedure for unclean shutdown
Last updated on APRIL 30, 2018
Applies to:Siebel System Software - Version 220.127.116.11  to 18.104.22.168 SIA [Release V7 to V8]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 22.214.171.124 
Database: Oracle 126.96.36.199
Application Server OS: IBM AIX 5L
Database Server OS: IBM AIX 5L
This document was previously published as Siebel SR 38-952176351.
***Checked for relevance on 22-Mar-2013***
We are working on our server autorestart and HACMP scripts for siebel. We have noticed, that if our ssh session has X11 packet forwarding checked, the stop_server command fails, waiting for an X11 server to receive requests. When we turn off X11 packet forwarding on our ssh session, then this is not a problem.
How do we work around this, in case somebody who is running a shutdown happens to have X11 packet forwarding on? There should be no dependency to X-windows on the shutdown scripts.
A related problem:
This problem occurs in our automated hacmp shutdown scripts - it calls siebel_server stop. If the siebel_server stop command hangs, because it cannot connect to an X-server, or for any other reason, then hacmp will not work correctly. I have set up commands to kill siebel processes and IPC's if this occurs. However, what commands do we have to run to cleanup any remnants of siebel in AIX memory, for example, if we have to kill the Siebel processes and IPC's manually?
What sequence of commands should be run, and what does each command do? (Ex. slibclean, reset_server, etc)
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