Tuesday, 24 May 2016

System Monitoring


What is System Monitoring?


System monitoring is a daily routine activity and this document provides a systematic step by step procedure for Server Monitoring. It gives an overview of technical aspects and concepts for proactive system monitoring. Few of them are:
  • Checking Application Servers.
  • Monitoring System wide Work Processes.
  • Monitoring Work Processes for Individual Instances.
  • Monitoring Lock Entries.
  • CPU Utilization
  • Available Space in Database.
  • Monitoring Update Processes.
  • Monitoring System Log.
  • Buffer Statistics
Some others are:
  • Monitoring Batch Jobs
  • Spool Request Monitoring.
  • Number of Print Requests
  • ABAP Dump Analysis.
  • Database Performance Monitor.
  • Database Check.
  • Monitoring Application Users.

How do we do monitor a SAP System ?


Checking Application Servers (SM51)


This transaction is used to check all active application servers.

Here you can see which services or work processes are configured in each instance.

Monitoring Work Processes for Individual Instances SM50:


Displays all running, waiting, stopped and PRIV processes related to a particular instance. Under this step we check all the processes; the process status should always be waiting or running. If any process is having status other than waiting or running we need to check that particular process and report accordingly.

This transaction displays lot of information like:
  1. Status of Workprocess (whether its occupied or not)
  2. If the workprocess is running, you may be able to see the action taken by it in Action column.
  3. You can which table is being worked upon
Some of typical problems:
  • User take long time to log on/not able to logon/online transaction very slow. This could be the result of the DIA work processes are fully utilized. There could be also the result of long running jobs (red indicator under the Time column). If necessary you can cancel the session by selecting the jobs then go to Process>Cancel Without core. This will cancel the job and release the work process for other user/process
  • Some users may have PRIV status under Reason column. This could be that the user transaction is so big that it requires more memory. When this happen the DIA work process will be 'owned' by the user and will not let other users to use. If this happens, check with the user and if possible run the job as a background job.
  • If there is a long print job on SPO work process, investigate the problem. It could be a problem related to the print server or printer.

Monitoring System wide Work Processes (SM66)


By checking the work process load using the global work process overview, we can quickly investigate the potential cause of a system performance problem.

Monitor the work process load on all active instances across the system

Using the Global Work Process Overview screen, we can see at a glance:
  • The status of each application server
  • The reason why it is not running
  • Whether it has been restarted
  • The CPU and request run time
  • The user who has logged on and the client that they logged on to
  • The report that is running

Monitor Application User (AL08 and SM04)

This transaction displays all the users of active instances.

Monitoring Update Processes (SM13)


Execute Transaction SM13 and put '*' in the field USER and click on  button.
 

If there are no long pending updates records or no updates are going on then this queue will be empty as shown in the below screen shot.
 

But, if the Update is not active then find the below information:
  • Is the update active, if not, was it deactivated by system or by user?
    • Click on  button and get the information.
    • Click on  button and get the below information:
  • Is any update cancelled?
  • Is there a long queue of pending updates older than 10 minutes?

Monitoring Lock Entries (SM12)

Execute Transaction SM12 and put '*' in the field User Name

SAP provides a locking mechanism to prevent other users from changing the record that you are working on. In some situations, locks are not released. This could happen if the users are cut off i.e. due to network problem before they are able to release the lock.

These old locks need to be cleared or it could prevent access or changes to the records.

We can use lock statistics to monitor the locks that are set in the system. We record only those lock entries which are having date time stamp of previous day.
 

Monitoring System Log (SM21)

We can use the log to pinpoint and rectify errors occurring in the system and its environment.
We check log for the previous day with the following selection/option:

2 comments:

  1. My friend Suggest me this blog and I can say this is the best blog to get the best knowledge.Thank you so much for this SAP Basis Training in Chennai blog

    ReplyDelete
  2. Thanks for the great information, was looking for this information from long.Great blogSAP MM Training in Chennai

    ReplyDelete