SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs Headline Animator

SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs


Friday, 16 September 2011

SAP System Log

This article answers following queries:

  • What is System log? How it will be useful?
  • How to check system log in SAP?
  • How to check all remote systems log in SAP?
---------------------------------------------------------------------
System Log:
In an SAP system, for every important action system log will get updated. So, in case of any issues with the system, basis administrators need to check the system log first to identify any errors or warnings.
Many times, we can resolve system issues by checking the system log and searching for relevant notes in the market place using keywords found in the system & applying them.  
In case of issues like update failure, lock table overflow, spool overflow, operating system issues, network issues, table space full issues and other database issues system log will get updated with the error message and the relevant time stamp. By using this timestamp and error message, basis administrator can identify the cause for the issue and can fix the issue.
 Based on the issue and the time stamp in system log, in many cases, you can find out relevant ABAP runtime dumps in ST22 (which provides much more detail about the issue) and the issue can be tackled accordingly.
How to check System Log?
System log can be checked using SM21 transaction code. Login to SAP system and goto SM21 which results in the similar screen as below:





As shown in the above screen, we can mention From date/time and To date/time and we can view system log based on problem classes.
As shown in the above screen there are 3 problem classes

  • Problems Only 
  • Problems and warnings
  • All message
Based on the requirement, any one of the above problem classes can be selected.
By default, User text box is left empty. It means it displays system log related to all the users. In case you would like to view system log of any specific user, you can mention the user id there.
After providing these input selections, to view the system log of the application server on which you have logged on, please click “Reread system log” pushbutton (which was highlighted in red). It displays similar screen as below:




As shown in the above screen, in the system log you can view following information:


  • Time Stamp
  • Type of work process
  • System Number
  • Client Number
  • User id (who executed the transaction)
  • Tcode  executed
  • Priority
  • Text related to the issue
Based on al l the above details, basis administrator can figure out the issue. In most cases, if additional details are required related to dumps, they can check in ST22 transaction.
How to check All remote system logs?
Please note the above process of checking system log is for only one application server (i.e. dialog instance) in which we have logged in.
If your sap system is a distributed system comprising of many instances/application servers, it would be difficult to log in to every instance separately and checking system log. To overcome this, SAP has provided an option of checking all remote system logs (i.e. logs of all instances of an SAP system) in SM21. So, using this by logging into any instance of an SAP system, logs of all other remote instances can be checked. By default, this option is not enabled.
To view “All remote system logs”, navigate as shown in below figure in transaction code SM21





After choosing “All remote system logs” option as above, pls provide selection criteria and click on Reread system log pushbutton to view logs of all instances of an SAP system as shown below









Enter your email address:


Delivered by FeedBurner

Thursday, 15 September 2011

How to check transactional RFC(tRFC) related errors?

This article answers the following queries :


  • How to check transactional RFC (tRFC) related errors?
  • How to find out status of transactional RFCs(tRFC) in SAP?
  • What is the transaction used to perform transactional RFC checks?
  • How to re-process failed or stuck LUW related to transactional RFC?
  • How to delete a transactional RFC related LUW from sap system?
  • How to reprocess all the transactional RFCs or LUWs that are stuck in SAP system at a time?
-------------------------------------------------------------------------
Transactional RFC related checks and maintenance can be done using SM58 transaction code
Sometimes, in real time scenario you can face following issues :

  • Process chain related performance issues in BIW system due to transactional RFCs stuck in R3 system.
  • Idocs flow not happening from R/3 to XI system

In these scenarios, SM58 transaction code will be useful to find out stuck tRFCs and action them accordingly.
Please login into SAP system and use SM58 as shown below :



Using  SM58, we can select TRFCs based on

  •  Any  2 dates
  •  User id
  •  Function of TRFC
  •  TRFC Destination
  •  TRFC Status

If you would like to list all, then use * as input in these fields

In the following screen, you can see the list of TRFCs that are waiting to be processed or stuck tRFCs as shown below





We can delete or re-process these LUWs based on the scenario. This can be done by navigating to Edit menu as shown below





You can reprocess an tRFC  LUW, by selecting the same and  by navigating to Edit -> Execute LUW. This can also be done by  pressing F6 button.

An LUW can also be debugged by navigating to Edit -> Debug LUW option
In case large number of tRFCs are stuck, all of them can be processed at a time by selecting
Edit -> Execute LUWs option as shown in the above screen.


You can also directly goto QRFC administration and QOUT scheduler from  SM58 transaction  as shown in the below screen.


















Enter your email address:


Delivered by FeedBurner

Wednesday, 14 September 2011

LiveCache Monitoring

This article answers following queries:

  • What are the monitoring checks for live Cache in SCM or APO System?
  • How to check “Activity Overview” in Live cache system?
  • How to check OMS locks in live cache system?
  • How to check SQL locks in live cache system?
  • How to check exclusive waits in live cache SAP system?
  • How to check database manager messages in live cache system?
  • How to check the parameters in live cache system?
  • How to check parameter history in live cache system?
  • What are the different memory areas in live cache system?
  • How to check Caches, Heap usage, data area and Log area in Live cache of APO   or SCM system?
-----------------------------------------------------------------------------------------
This article explains you how to monitor/view  various paramaters, parmeter history, OMS locks, SQL locks,  cache usage, exclusive waits, database messages, various configuration related to memory. This knowledge will be very much useful to troubleshoot and fix the problem  in case you encounter any  performance issues in Livecache system.
Please login into livecache system using LC10 transaction and providing LCA in the name of database connection as below. Click on Pushbutton “Livecache Monitoring” to proceed further.


System redirects to the following screen.  As shown, in the screen, please click on “ Activity Overview” item  to view details/statistics  related to

  • SQL Statements
  • I/O Activity
  • Lock Activity
  • Logging Activity
  • Scan and Sort Activity





To view OMS locks (or logical object locks) , navigate to LCA->  Problem Analysis ->  OMS locks -> Overview  as shown in the  below screen.





To view exclusive waits, navigate to LCA -> Problem Analysis -> SQL Locks -> Waits as shown in the below screen





To view existing SQL Locks and SQL lock requests, navigate to LCA -> Problem Analysis -> SQL Locks -> Overview as shown in the below screen





To check database manager messages, navigate to LCA -> Problem Analysis -> Messages -> Database Manager as shown in the below screen.





To view the defined parameters and their values in the live cache system, navigate to LCA -> Administration -> Configuration -> Parameters  as shown in the below screen






To view the history of the parameters that are changed date wise, navigate to to LCA -> Administration -> Configuration ->Parameter History as shown in the below screen





To view the Cache related information, navigate to LCA -> Current Status -> Memory Areas -> Caches as shown in the below screen.



To view the OMS Heap  related information, navigate to LCA -> Current Status -> Memory Areas -> Heap Usage  as shown in the below screen.

To view the “ Data area”  related information, navigate to LCA -> Current Status -> Memory Areas -> Data Area  as shown in the below screen.





To view the “ Log Area ”  related information, navigate to LCA -> Current Status -> Memory Areas -> Log  Area  as shown in the below screen.





Related Link :







Monday, 12 September 2011

How to start or stop live cache in SCM or APO SAP systems?

This article answers following queries:

  • How to start or stop live cache in SCM or APO SAP systems?
  • What is the transaction used to administer livecache in SCM or APO systems?
  • How to monitor livecache in SCM or APO systems?
  • How to check operational state of livecache in SCM systems?
  • How to check when was the last date on which live cache started in SCM system?
  • How to check live cache related alerts in SCM systems?
  • What is the database on which livecache runs on SCM systems?
  • What is the start/stop sequence of livecache?
  • How to check the live cache version?


-------------------------------------------------------------------------------------------

STOP sequence of livecache in SCM or APO system:
Sometimes to perform any maintenance it is required for basis administrator to shut down the SAP system. If an SAP system consists of livecache then it is required to know the sequence in which system to be bought down to avoid issues

Shutdown sequence:

  • First of all shutdown livecache (Process explained below)
  • Shut down ABAP system (as per the standard process of shutting down any SAP system)
  • Shut down Database system ( as per the standard process)

START sequence of livecache in SCM or APO System:
Start sequence of livecache system is exactly reverse order of shutting down process.

Start sequence:

  • Start Database of the SAP SCM system (As per standard process)
  • Start the ABAP stack (As per standard process)
  • Start the live cache (process explained below)

How to Check the live cache Operational State :
Login to SAP system and goto transaction LC10.
Systems displays screen similar to below. Please select name of database connection as LCA and click on "Livecache: Monitoring" tab to proceed further. 


After this, you will be redirected to the below screen. Here you can check the operational state of the live cache. It is green currently. It means live cache is up and running.


 From the below screen, we can determine


  • live cache version
  • live cache operational state
  • Database server version
  • Operating system
  • What was the date/time at which livecache started in this system
  • When was the last livecache start/stop activity done
  • Automatic log backup is on or off
  • Database Trace/Command monitor/Resource monitor on/off status
  • Different directories/files belonging to livecache





Note : By clicking on the Alert monitor link (as shown in above screen), we can check various alerts that are belonging to livecache.


Once you click Alert monitor, it opens another screen as below. From here you can click on "open alerts" pushbutton to view all the alerts related to livecache. In addition to that, we can drill down on various parameters in the below screen and we can identify problematic areas.

If there is an issue in any area, that will be highlighted in red as shown in screen below






































How to Stop LiveCache:

To stop the livecache, In this screen, navigate to Administration -> Operating and click on "Stop livecache" pushbutton  (as shown in the below screen). 
 Once the livecache got stopped, the operational state button which is green earlier will turn to red confirming that the live cache is down.






How to Start LiveCache:


To start the live cache again, navigate to Administration -> Operating and please click "Start Livecache" pushbutton in the above screen.

Once the livecache started successfully, its operational state turns into green color indicating that livecache is up and running.

Please note that live cache runs on a MAXDB database.

Related Link :


How to start or stop live cache in SAP SCM or APO system?









Enter your email address:


Delivered by FeedBurner