Problem Statement : Siebel servers are not shutting down after executing the stop_server all command and the error which is frequently observed is “server not shutting down” or “server services could not be shut down”.

Health of these siebel server processess play major role to keep the application and other operational functionalities smooth and fine. "Process" is a collection of many "Tasks" or "Threads". All these threads are defined within a process, under a specified parameter within the siebel server for different functionalities.
Example: MaxSharedDbConns , MinSharedDbConns

In day to day life Siebel application developer has to deal with scenarios where few functionality or some configuration is making Siebel application latent. Developer has to extract the SQL queries to analyze the problematic functionality. We are sharing structured steps to analyze and extract the SQL queries which are leading to latency in Siebel application

Siebel Application Response Management (SARM) is a framework for identifying performance problems in the Siebel enterprise application. SARM allows administrators to collect critical performance and timing data,