alternateplanet

The Following are the transaction codes used for the System Monitoring:
SM12:
This Traction is used for Check for Lock Entries. There may be old locks still in place from transactions that did not release, or from when the user was cut off from the Network. If any lock entries are exist then we have to check since how long this lock existing. If, this lock existing from more than one day then we should check that particular User is available or not (By using the Transaction Code AL08). If he is not available then Delete that lock. Otherwise we should wait 1 or 2 Days.

SM13 :
This Transaction is used for Check for any Errors in Update Records. A failed or “Update Terminate” is an update to the failed database. These failed Updates occurs when a user entry or transaction is not entered or Updated in database. And we should check Whether Update is ACTIVE or not. And also we should check any Update Records are terminated.

SM21 :
This Transaction is used to check System Logs. After hitting the traction we should goto System log–> Chooseà All Remote System logs, and set Date and time to before the Last log review. And we should check whether any Errors, Warnings, Security Messages, Database, Abends, Any other different Events are there.The log is important because unexpected or unknown warnings and errors could indicate a serious problem.

SM51 :
This Transaction is used to check that all Application Servers are UP. And also This transaction is a central transaction from which you can select the instance to be monitor.

SM50 :
This Transaction is used to check Work Process Overview and for Systems with out Servers. Here all work processes with a “Running” or “Waiting” State. If Batch Jobs are not Running, If all the work processes are in use, this transaction provide a hint of this problem.

ST01 :
This Transaction is used for System Trace. By this transaction we can trace that what are the operations performed on particular file by particular user on which dates.

ST02 :
This transaction is used for Buffer tuning or Buffer Statistics. And it is used to tune Buffer perameters of R/3. The Buffer is important because significant buffer swaping reduces performance. Look under “Swaps” for Red Entries. Regularly check these entries to establish trends and get a feel of the Buffer behaviour. And in this transaction we should Maintain “Hit Ratio” is in between 90 – 100% for all , and “Heap Memory” allocated should be “0” , and “Swaps” is 0.

ST03 :
This Transaction is used to Check Work Load Analysis of . Workload Analysis is used to determine System performance. Check Statistics and Record Trends to get a feel for the System’s Behaviour and Performance. Understanding the System when it is running well helps us to determine what changes may need to be made when it is not.

ST04 :
This Transaction is used for Database Performance Analysis. This transaction provides the ability to Monitor the Database in related to 1) In Shared Pool “SQL Area Get Ratio” should be 90 – 95% 2) In Log Buffer Allocation Retries / Entries <1% 3) In Data Buffer “Quality” should be in 90 – 95% 4) In Sorts Disk / Memory <1% 5) In Table Scan & Fetches “Long Table Scans” should maintain as minimum as possible. And we should check Detailed Analysis then we should hit “Detailed Analysis menu” Button in this screen. In that we can check Database Overview like “Exclusive Lock Waits” , “Wait Events”, “Buffer Busy Waits”, “ File System Request”, “ Database Message logs”, “ SQL Requests”, Summery Report for all activities, etc

ST22 :
This Transaction is used to Analyse ABAP Dumps or Short Dumps. This transaction is also used for Analyse and Determine why the error occurred and take corrective action. It looks for an excessive number of dumps, and also dumps of an unusual nature. A ABAP dump is generated when a report or transaction terminates as a result of a serious error. The system records in the System Log(SM21) and writes a snapshot of the program terminate to a special table.

DB02 :
This transaction is used to check all table Spaces and Indexes. Here we should check table spaces sizes. If any table used space is =>99 then we should increase add the space for particular table space. And this transaction is provides a way to examine database allocation. And this transaction is allows us to monitor items such as: a) DB Space History b) DB Analysis By this transaction we can view Database history by Dates and Times.

DB12 :
This Transaction is used to check database Backups. And in this we should we see successful Backups and Unsuccessful Backups list

AL08 :
This transaction is used to Check the users on the System. This transaction displays User Ids and Terminal Names who are currently logged on the system.

SM37 :
This transaction is used for Monitoring Background Jobs. Background are batch jobs scheduled to run at specific time during the day. Here we should check for cancelled jobs. Here If we want to check particular job then,we should enter the Job Name and enter User name in User name field or ‘*’ and hit execute Button. And verify that all critical jobs are successful.

Export SAP Users and Authorizations:

1) Logon to the target SAP system in the client you want to save and go to transaction SCC8.

2) Select the SAP_USER profile and the Target System,

3) Click the Schedule as Background Job button and then check Immediately.

4) Click the Schedule Job button, click Continue.
If this system has more than 1 server, set Background Server to the Central Instance Server

5) Make a note of the KT transport number shown on the next window. The KT transport is for transporting client specific data.

6) The status of the export can be found using transaction SCC3.

7) After the export completes in SCC3, check the transport logs for the KT transport in SE01. The export is not finished until the “export” step shows completed successfully.

For systems with more than one client, you will need to follow the above steps on each client to create a transport of the users for each client.

Import SAP Users and Authorizations:

Note: This procedure assumes the Users were exported and Transport created before the client copy

1) Import the appropriate user Transport for each Client (i.e. 100, 900, 910 etc) from CMD Prompt .
Import needs to be done from CMD prompt (Not STMS), and while import is running, log off of the system as all IDs will be deleted and recreated with the import.

In the examples below a full system was assumed. If you are only importing users from a Client Copy there will only be one transport.

For All R3 Systems

tp addtobuffer xxxKT0aaaa u1 pf=

tp addtobuffer xxxKT0bbbb u1 pf=

tp addtobuffer xxxKT0cccc u1 pf=

tp addtobuffer xxxKT0dddd u1 pf=

tp import xxxKT0aaaa client pf=
tp import xxxKT0bbbb client pf=

tp import xxxKT0cccc client pf=

tp import xxxKT0dddd client pf=

2) After the import is complete, Logon to the SAP GUI for each Client as SAP*

Execute Transaction: SCC7

If a message pops up that this is a Production Client and protected from Client Copies

Go into SM31 and table T000 and change Client to “Test”

Ensure the Transport that is displayed is the Transport you imported in previous step

Select “Execute in Background”

Monitor to completion in Transaction: SCC3

Repeat this process for each Client Transport Exported/Imported

Change Target Client back to “Production” – If necessary

Transports in SAP are done using the tp command on the OS level, this post tries to explain the different modes available to further customize your import.

tp import transportrequest clientxxx U1
tp import transportrequest clientxxx U126
tp import transportrequest clientxxx U148

The u stands for unconditional force ( how hard you want to force the request into the system – do you want to overwrite without warnings, or softly try to load the objects).

0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.

1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.

2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.

3: When used with tp import, it overwrites the system-dependant objects.

5: During the import to the consolidation system it permits the source systems other than the integration system.

6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.

8: During import phase it ignores the limitations caused by the table classification.

9: During import it ignores that the system is locked for this kind of transport.

Why object locks?
The locks are used in sap to prevent concomitant change of an object by two developer.

The enque work process manages the locking system. The lock entries for data to be processed in lock table which is maintained in  main memory.

Various Lock Modes in SAP

Shared Lock (S):
Several users can access the locked data at the same time in display mode.
Requests for further shared locks are accepted, even if they are from other users.
Exclusive locks are rejected.

Exclusive lock (E):
The locked data can be displayed or edited by one user only.
Requests for either another exclusive lock or a shared lock are rejected.

Optimistic Lock (O):

An optimistic lock can be set if the data is displayed in change mode and the lock behaves like a shared lock if there are access collisions. But if the data is changed, the optimistic lock converts to an exclusive lock. 0ptimistic locks on the object then become invalidated. It can therefore be possible that the conversion fails, if beforehand another optimistic
lock was converted. In such cases the use of optimistic locks is only beneficial, if the probability that the data will NOT be changed is high.

Exclusive but not cumulative lock (X):

Exclusive but not cumulative locks can only be requested by the same transaction once only.
All further lock requests are rejected.