SM51: (Application Server)
Transaction code SM51 is to display list of active application servers that have registered in the SAP message server. Further, you can manage & display the status, users, work process in all application servers belonging to the SAP System.
• Processes: Display & control work process. [SM50]
• User: Display & manage user sessions. [SM04]
• SNC Status: Display SNC status.
• Release Notes: Display detailed release information for an application server.
• Remote Logon: Log on by any server in the system; you can see the server where you are logged on in the status bar in the second entry from the left.
• System Log: System logs. [SM21]
Source: http://itsiti.com/sm51-sap-server-overview
___________________________________________________________________________________
SM50: (Work process monitor - single instance)
Transaction code SM50 is used to monitor and manage work processes. In the work process overview, you can:
• End an ABAP program that is running.
• Debug an ABAP program that is running.
• Cancel a process (with or without core) – long running jobs
• End a session
• Activate/deactivate the restart option after an error
• Execute various functions for the process trace
___________________________________________________________________________________
SM66: (Work process monitor - overall instance) 2 states - waiting and running
Transaction code SM66 is used to quickly investigate the potential cause of a system performance problem by checking the work process load. You can use the global work process overview to:
• Monitor the work process load on all active instances across the system
• Identify locks in the database (lock waits).
Using the Global Work Process Overview screen, you 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
_________________________________________________________________________
ST22: (ABAP dumps)
You can use the tools of the ABAP dump analysis (ST22) to list the ABAP runtime errors that have occurred in an ABAP system as well as the relevant short dumps.
Displays and analyzes update statistics again
Save in a local file
Print
Store for a longer period of time
SM37: (Monitor background jobs, monitor overrunning jobs)
Transaction code SM37 is to monitor the background, batch jobs running in the system.
1. From the initial screen, you can search by the job name, user name or program name accordingly with the time condition.
Note
• Planned - Job already been defined, but the start condition has not yet been defined.
• Released - The job has been fully defined, including a start condition.
• Ready - The start condition of a released job has been met. A job scheduler has put the job in line to wait for an available background work process.
• Active - The job is currently running. Active jobs can no longer be modified or deleted.
• Finished - All steps that make up this job have completed successfully.
• Canceled - The job has terminated. This can happen in two ways:
- An administrator intentionally terminates the job
- A job step contains a program that produces an error, such as:
* an E or A error message in an ABAP program
* a failure return code from an external SAPXPG program
Source: http://itsiti.com/sm37-background-batch-jobs
__________________________________________________________________________________________________________________
SM04: (User monitor - single instance)
Transaction code SM04 shows the list of the users which are logged on to the instance in which are currently logged in. The total number of users and sessions are given at the bottom of the list.
Note
• Client: SAP Client.
• User: User logged on to server (SAP user name).
• Terminal: Terminal at which the user is working. (If it is a UNIX frontend, the terminal name corresponds to the display variable of the frontend process; if it is a Windows or OS/2 frontend, the terminal name corresponds to the host name on which the frontend was started.)
• TCode: Last executed SAP transaction (transaction code).
• Time: Time at which the user last initiated a dialog step by entering data.
• Sessions: Number of external sessions (session) opened by the user (up to 6). You can display detailed information on a session by selecting a user and choosing the Sessions button.
• Ty: Connection type (GUI, RFC or Plugin (HTTP or SMTP request).
• MByte: Size of the memory allocated to the user in megabytes.
Source: http://itsiti.com/sm04-user-list
__________________________________________________________________________________________________________________
AL08: (User monitor - multiple instance)
Transaction code AL08 shows the list of all the users who are logged on to the system globally or for all the instances in the system which are active.
• Active instance – Shows the Active instance.
• Active users – Displays the active users logged on to the active instance.
• Interactive users – Displays the Dialog users logged on to the active instance.
• RFC users – Display the users that are connected via RFC on the active instance.
• Mand – Client number.
• User – User name of users logged on.
• Terminal – From which Terminal/machine user has logged on.
• T-code – Last executed transaction code.
• Time – The time when a user last initiated a dialog step by entering data.
• External Sessions – Number of External sessions the user has opened. It use SAP memory to share data between external sessions and it based on per main window. An external session is started when starting a program and when ever the use of CALL TRANSACTION. Each user can open maximum 6 SAP system windows in a single SAPGUI session. Each of these windows corresponds to a session on the application server with its own area of shared memory. The session can be created by System -> Create Session.
• Internal Sessions – Number of Internal sessions the user has opened. A session that with in external session. There can be many internal sessions in an external session. ABAP MEMORY is used to exchange the data between internal sessions. When calling a program using SUBMIT or CALL Transaction, it will be loaded in a new internal session.
Source: http://itsiti.com/al08-list-of-all-users-logged-on
__________________________________________________________________________________________________________________
SM13: (Update Process)
Transaction code SM13 is a update management transaction which is used for:
• Display update requests
• Analyze problems pertaining to the update
• Test and debug canceled update requests
• Display and reset the status of update requests
• Delete update requests
• Display statistics on updates
__________________________________________________________________________________________________________________
SM12: (lock entry monitor)
The SAP System is equipped with a special lock mechanism that synchronizes access to data on the database. The purpose of the lock mechanism is to prevent two transactions from changing the same data on the database simultaneously. Lock entries are usually set and deleted automatically when user programs access a data object & release it again. The lock mechanism is closely related to the Update Mechanism.
1. You can use SM12 to check and delete lock entries.
2. In SM12, check any lock entry older > 2 days. If any outdated entry found, check the corresponding user is user online/offline in AL08 or SM04 (you can get the transaction code that been use by the user). Get the user contact from SU01 and inform about the lock else if the user is offline, release the table from lock by deleting the lock.
__________________________________________________________________________________________________________________
DB12: (Database monitor, backup check, Backup logs overview)
Transaction code DB12 is to collects and presents information that is necessary to monitor database backups. It is an important source of information for the database administrator who has the task of supervising the execution of a defined backup strategy.
On the initial screen of the monitor, it shows overview of important information related to SAP database backups.
• The last successful backups for the SAP, master and msdb databases and transaction logs.
• The last SAP database size and duration of the backup job.
• Whether the SQL Server Agent is started or not.
• The amount of log space allocated and how much is still free.
• The Recovery interval, which specifies the maximum time that SQL Server should spend recovering after a database startup.
No comments:
Post a Comment
If you have any doubts, Please let us know.