You are on page 1of 15

SAP Basis Daily Monitoring

10/01/2013

Srividhya Srinivasan
SAP BASIS
sri.s@tcs.com

are self-regulated by a Code of Conduct as enshrined in the Tata Code of Conduct. This information may not be disclosed. We request your support in helping us adhere to the Code in letter and spirit. The information contained in this document may not be released in whole or in part outside TCS for any purpose without the express written permission of TATA Consultancy Services. .Confidentiality Statement Include the confidentiality statement within the box provided. duplicated or used for any other purposes. This has to be legally approved Confidentiality and Non-Disclosure Notice The information contained in this document is confidential and proprietary to TATA Consultancy Services. in our dealings. Tata Code of Conduct We. We request that any violation or potential violation of the Code by any person be promptly brought to the notice of the Local Ethics Counselor or the Principal Ethics Counselor or the CEO of TCS. All communication received in this regard will be treated and kept as confidential.

...................................................... 13 5........................................................................................................................................................................................................................................................................................................1 File System ...................................................................................................................................................................................................................................... 5 SM21: (System log) ............................................................................................................................................................. 6 SM13: (Update Requests overview) ................................................................................. Summary .2 CPU and Memory Usage ................................................... 7 DB12 (Backup logs).......... 4 SM12: (Lock entry list)................................................. 12 4............................................................................................... 12 3...... 4 2......................................................................................................................................................................................... 14 .................................................................................................................................................................................................................. ABAP Stack Checks ........................................................................................................................................................................................................................................ 4 SM66: (Global process overview) ....................................... 8 DB13 (DBA Planning calender) .......................................................................... 11 3.................................................................................................................................................................................... 4 SM50: (Process Overview) ...................... 10 SP01 (Check Spool status)......................................................... 4 SM51: (Application servers status)................... Max DB Checks............................................................................................................. 6 ST02: (Tune summary) ............................................................................................................................................................................................................................................................................................................................. OS Level Checks................................................................................. Introduction........................... 5 ST22: (ABAP Dumps) .......................... 9 ST04 (Database alert logs and performance) ...................... 8 DB14 (DBA operations log) ............................................................................................ 12 3................................................................................................Table of Content  1..

Monitoring can be focused on ABAP stack checks includes database checks. MAXDB checks and Oslevel checks. 2. Upd2. SM66: (Global process overview) This transaction code will be useful to view the processes that are running across all instances/application servers of a SAP system. The work processes can be increased based on the memory availability. Batch. . In this view you can check whether there are free work processes to execute the processes. If you find that there are no free work processes for maximum times that you may consider. If any application server is down. improving profitability of the business organization. Update. increasing the number of work processes. Similar to SM50 checks can be done in this transaction as well. Spool. Introduction Proactive monitoring of the SAP systems will help to understand issues in advance & helps us to take corrective actions and thus will lead to lesser downtime of the systems. SM51: (Application servers status) This transaction code will be useful to view all the hostnames and application server status.1. ABAP Stack Checks   SM50: (Process Overview) This transaction code will be useful to view the processes that are running currently in a sap instance. This change will get reflect after system restart. the same can be identified using status of the server column. We can also figure out different Message types (Dialog. If all the work processes are in running state and no work process is idle it means that wait times will increase for the processes that are waiting in the dispatcher queue leading to performance degradation. ICM etc) configured for the respective servers.

A lock can be set for such a long duration due to a long running background job or a lock is not released due to an application error or a program terminated abruptly but lock not released etc. If any such locks. Some of the examples of abap dumps are timeout issue. we need to look for any old sap locks that are more than 1 day. it is the responsibility of the basis administrator to analyze the dumps and take necessary actions to avoid issues.SM12: (Lock entry list) This transaction code will be useful to view all the sap locks that are present in the system. As part of monitoring. As part of daily monitoring. We can view dumps by selecting Standard and Own selection view. ST22: (ABAP Dumps) This transaction code will be useful to view all the abap dumps that have occurred in the system on a given day. spool overflow issue etc . we need to analyze the reason for that lock for such longer duration and take actions accordingly. database space issue.

SM13: (Update Requests overview) This transaction is useful to figure the status of update system. spool overflow. message server issues.SM21: (System log) This transaction is useful to view the log of the sap system for various operations. SM14 transaction can be called internally from SM13. analysis to be done whether to repeat update. This log will be very useful to identify various issues in advance and to take necessary measures. These both transactions are useful for update administration. all) and time interval during which you would like to view the status execute to check the overview of updates as per the status and time interval selected. v2 executed. In SM13. In case an update is inactive we can figure out the same from this transaction and necessary action can be taken and update can be activated again. lock table overflow etc issues. database space issues. System log is the place to check out for any timeout. . to be updated. you can select status (canceled. v1 executed. In case of canceled updates. network issues.

Page area. swaps.Buffer statistics like hitratio.Important statistics related to Roll area. . Extended memory and heap memory . This needs system restart to make it as permanent change. it is our responsibility to ensure there is more hit ratio for the buffers and less swaps to ensure efficient performance of the sap system.Call statistics like select. insert. update and delete As a basis administrator. In case you see there are more swaps and less hit ratios for most of the buffers. then tuning buffers to be carried out to ensure optimal performance based on system configuration.ST02: (Tune summary) This transaction will be used to monitor . db access details. size of buffer and free size of buffer etc .

verify database. . initialize tape and validate structure jobs).Overview of redolog files (Number of redologs that are not yet backed up) .DB12 (Backup logs) This transaction is useful to check the details of . compress database. incremental backup offline/online. redolog backup.Archiving directory status (Free space of oraarch) .Overview of database backups (Success / failure of backup with log details) .Last successful backup . Full backup online/offline. update statistics. check db. cleanup logs.Overview of redolog backups (Success / failure of backup with log details) DB13 (DBA Planning calender) This transaction will be useful to schedule various database backups & clean up jobs like (whole database backup offline/online.

. SAP basis administrator should use this transaction to find out canceled jobs and active jobs (for eg: long running .more than 24hrs etc). DB14 (DBA operations log) This transaction will be useful to check the status of following: .Redolog backup .In this transaction.Database backup .BRCONNECT operations (Update optimiser statistics. you can also check the status of every job that was scheduled and can reschedule in case of failures. In case of failures. SM37 (Job status overview) This transaction will be useful to have an overview of jobs with different statuses. As part of daily monitoring. should figure out root cause and take actions like rescheduling and ensure these jobs are successful. database check etc) As an sap basis administrator it is our responsibility to check and ensure backups and other cleanup jobs are successful everyday.BRSPACE log (extend tablespace issues etc) .

we can even select the jobs based on start condition. re-triggering backup etc Under Alerts.Backup/restore .In case of canceled jobs. external command or external program). you can view Alert monitor that will summarize status of the database under different heads like .Performance . period etc ST04 (Database alert logs and performance) This transaction will be useful for (oracle) database administration. STATS_TOO_OLD. go to Alerts and drill down further. root cause for the failure to be figured out from the logs of the respective job and to be actioned by rescheduling etc. steps (like abap program. using extended job selection option.Space Management . After going through the error or warning in details take necessary corrective actions based on the error like running update stats again. LAST_BACKUP_FAILED. In case of long running jobs. LAST_ARCHIVE_FAILED etc. Click on "Database Check" to find out any errors or warnings related to database like MISSING_STATISTICS. In SM37. we need to figure out the reason for long running and action them accordingly.Health . In this screen.SAP Consistency .

Then it is the responsibility of Basis administrator to take necessary actions on the same. SP01 (Check Spool status) This transaction is useful to find out the status of spool request and output request. you can see Space management in red color. you can list the spool requests or output requests between a given intervals. These are color coded for ease of administrator (Red for errors. check out whether there is any spool overflow. For eg: if so many spools are in waiting status. figure out if there is any network issue and take necessary actions. yellow for Warnings and Green for OK status) For Eg: If PSAPSR3 tablespace is >90%. . If many spools are in error status. find out whether output device is available or not. you can check out the status of spool requests and find out any errors by drilling down further. In SP01 transaction.Drill down on each of these to find out potential problems. In the list generated. If customers complain that they are not able print anything from SAP.

df –gt | grep <SID> 3. It gives Idle CPU time from which we can calculate the actual usage. The command can be used is ‘topas’ at OS level. /usr/sap/<SID> /sapmnt/<SID> /oracle/<SID>/sapreorg /oracle/<SID>/saparch /oracle/<SID>/oraarch Command to look FS capacity is. The important mount points are. log and archive files. real memory usage and paging memory usage.2 CPU and Memory Usage We need to check CPU usage.1 File System   We need to check the File System capacity of important mount points in each server for each system. If it is go beyond 80% we need to take some action to reduce the used space.3. Possible files might be some of the old core. OS Level Checks   3. .

Max DB Checks We need to check MAX DB systems online status.Backup History         .Data area .4. We should also check the backup history whether the backups are executed successfully.State . The data area should not go beyond 85%. . We can add data volume to reduce this. log area and data area. Attributes to be checked are.

checkdb etc 9 (DB13) 10 Check for long running/failed jobs status (SM37) 11 Check database alert logs and performance (ST04) 12 Check spool job status (SP01) Os level checks 1 Check file systems usage (should be <80%) 2 Check for swap space using topas etc MAXDB checks 1 System Availability 2 Backup History .5. Summary Please find below table that summarizes daily monitoring tasks that are to be performed by the SAP Basis Administrator: Sno Task ABAP Stack Checks 1 Check process overview (SM50) 2 Check overall system process overview (SM66) 3 Check application servers status (SM51) 4 Check for any pending locks (SM12) 5 Check for Dumps in the system (ST22) 6 Check System log for any errors (SM21) 7 Check for any hanged updates or update status (SM13) 8 Check for excessive swapping (ST02) Check for critical job status like backup. updatestats.

 India’s largest industrial conglomerate. and could result in criminal or civil penalties. TCS offers a consulting‐led. uploaded. modified. This is delivered  through its unique Global Network Delivery ModelTM. reproduced. ensuring a level of certainty no other firm can match. transmitted. Unauthorized use of the content / information appearing here  may violate copyright. recognized as the benchmark of excellence in software  development. A part of the Tata Group. posted or distributed in any form  without prior written permission from TCS.Thank You About Tata Consultancy Services (TCS)  Tata Consultancy Services is an IT services.tcs. visit us at www. TCS has a global footprint  and is listed on the National Stock Exchange and Bombay Stock Exchange in India.   Copyright © 2011 Tata Consultancy Services Limited  .  The content / information contained here is correct at the time of publishing. No material from here may be  copied. For more information. engineering and assurance services.com. trademark and other applicable laws.  integrated portfolio of IT and IT‐enabled infrastructure. consulting and business solutions organization that delivers real  results to global business. IT Services  Business Solutions  Outsourcing  All content / information present here is the exclusive property of Tata Consultancy Services Limited (TCS). republished.