1)Critical blocking Sessions solutioon=: Blocking sessions will give the PID number (wok process ID), CLIENT NAME=user name, table names. Based on these details we will identify the which work process being running and it’s number,PID from SM66 transacion. Now we will identify the work process session and get the details overview of that Job, what the Job is performing in the system and impact of this Job to the Business if we can cancel it. Then we will notify the Functional teams or Job owner’s about this Job and it’s blocking sessions on database tables(DB01). We will not wait for more than 10 mins for the Database Blocking sessions because these locks will hold the DB objects and apply the lock mechanism on it and caused other processes to be wait until the first Job completes. In this case other Jobs or users facing the HOLD & WAIT(Deadlock) situation. 2) Java WEBLINK Down (or)server node down solution= Solution: whenever the Java server nodes are down, immediately we will check the MMC and corresponding Java server nodes and see the status of server node .If we see the server node status as stopped then we will restart the corresponding server node by JCMON or JSMON tool. Reasons for server node down: 1.server node may be unresponsive due to Full GC situation or GC or Heap Dump occur. 2.Max thread count reaches 3) ECC Table modifications . solution= : we can modify the SAP table using SM30. We may get Form 119’s for PRD changes like file placing or moments or rename or remove. 4)High number of user locks in ECP solution=Check the SMQ1 queues count and try to find if any of one of them in SYSFAIL state or stuck then we can move the error out queues into TRFC and for the stuck queues, we just lock & unlock the stucked queue then activate it so that stucked queues can be processed. 5): High CPU Utilization on server solution=check what is being activated in the system or running through SM66 and then notify the Job owners about the Job’s priority and impact of them running in Business hours.Ask them about expected end time to complete the Jobs .Also if those jobs are not important then we can Kill them after getting confirmation from Business people means Job owners. 6) Long running Jobs solution =: Check the Job details through SM50 and find the cause whether it is Sequential or Direct Read and Job type means which is related to Payroll or extraction or tables update etc, and then notify the Job owners about current situation. 7) Users unable to login through GUI solution=: Goto DPMON-> Identify the work processes history and current status of DIALOG work processes then kill the few of the work processes whichever got stuck or hung.Ask them to try now. 8)Activate the web services through SICF. solution=Goto SICF transaction -> select the service->Right click->Activate it 9)Import running longer time in STMS solution=check the file system space /usr/sap/trans/EPS/in/ and check the TP connectivity(tp conncect SID) and database conncection to SAP by r3trans –d.