How to set up and troubleshoot early watch alerts in Solution manager 7.1 or 7.2?

This article answers following queries:

• How to configure Early watch alert report in Solman 7.1 or 7.2?
• How to set up and troubleshoot early watch alerts in Solution manager 7.1 or 7.2?
• How to configure automatic email transmission of early watch report in solman7.1 or 7.2?
• How to schedule EWA in Solman 7.1 or 7.2?
• Early watch Alert management

=====================================================

Have received many requests asking to explain me the process of configuration or setup of early watch alerts in solution manager 7.1. There is standard sap note: 1907383 readily available, which explained this setup in detail.

I’m uploading this note below. Please go through the same.

https://drive.google.com/file/d/0B4VnuFzPej3iTmZicGZNeWw1dk0/view?usp=sharing

How to troubleshoot when no one is able to login to SAP system (ABAP stack)?

This article answers the following queries :

• How to troubleshoot when no one is able to login to SAP system (ABAP stack)?

• What could be the reasons if no one is able to login to SAP system (ABAP stack)?

Sometimes users may complain that they are  :

i)       Unable to login to SAP system from SAPGUI

ii)      Other users who have already logged in may complain that system is not responding

iii)    Some users who have already logged in may complain that system is very slow and response time is very high

Please note that in most of the above cases even SAP basis administrator cannot login to SAP system through GUI. So, he should use database, operating system tools (like PuTTy) and dpmon to identify the issue and troubleshoot.

The most likely reasons for all the above scenarios could be

i)          Oraarch is full and system is not able to respond to user queries due to that and all dialog processes are occupied within a while due to that and system is not allowing any other users to login due to lack of dialog workprocesses

Solution :  As even basis administrator cannot login through SAP GUI at this point of time, Please check at operating system level. If you find that oraarch filesystem is 100% full, please trigger archive log backup immediately and make sure there is enough space. Once there is sufficient space, system will start processing and all the dialog users activities will be resumed and within a while there will be free  workprocesses to login and issue will get resolved

ii)           Some critical filesystem at Oslevel is full and system is not able to perform any activity due to that. Within a while all the dialog workprocesses are full and no other user is allowed to login

Solution :  As even administrator cannot login through SAP GUI at this point of            time, Please check at oslevel whether any filesystem is 100% full. If so, please contact OS team and make sure sufficient space is free either by requesting them to add  more space or by deleting some unnecessary files

iii)        Some tablespace like PSAPSR3 is 100% full and system is not able to perform requests of existing users. Within due time all the workprocesses will get occupied and system will stop responding and it won’t allow any other new user to login due to lack of free workprocesses

Solution :  (In Unix related Operating systems (AIX, HP-UX), login to system                 through <ORASID> user and run brtools to run whether any tablespace is 100% full. If so, please add some datafiles and make sure sufficient free space is created. After that system automatically resumes processing.

iv)    Update got deactivated and system is not able to perform updates and thus all dialog/background workprocesses are full within due time and system is not allowing any other users to login

Solution : In some cases, in all the above error cases i) , ii) and iii) , SAP system may deactivate update automatically to prevent loss of data. So, after fixing the respective issue, we need to manually activate the update through SM13 so that system will resume processing. But you can activate the update only if system allows you to login through SAP GUI.

If you are not able to login to SAP system through SAPGUI, please use dpmon tool to do the same.


How to use dpmon tool

v)          Other scenario could be some processes has gone into PRIV mode consuming so much memory. This leads to memory bottlenecks and all other users requests will either take lot of time to process thus experiencing slowness or high response times.

After a while it also may happen that all dialog workprocesses got full and no other user will be able to login due to lack of free workprocesses

Solution :  This has 2 scenarios :

i) If you are able to login to SAP system through SAPGUI, please goto SM66 and identify the processes that have gone into PRIV mode. After identifying the transactions that are being run in PRIV mode, please check with respective user and terminate the processes or logoff the users from the system after confirmation that his process is non critical and can be terminated.

Terminating user session

ii) If even basis administrator could not login to SAP system, then use dpmon tool to identify the processes that have gone to PRIV mode.

How to use dpmon tool ?

 After identifying processes that have gone to PRIV mode, cross check with the user and after confirmation that his session can be terminated, kill his session by providing PID number

For example: In AIX or HP-UX use command below

Kill -9 <PID>

In the above command, PID is process identification number.

After that system will release all the memory allocated to PRIV mode processes and will sytem will start processing normally.

Enter your email address:


Delivered by FeedBurner

Troubleshooting long running transport

This article answers the following queries :

• How to troubleshoot when a transport is running for unusually long duration and not getting completed or terminated ?

• How to troubleshoot when a transport is in truck status for a long duration of time ?

• How to cancel a transport request which is in truck status or running status ?

• How to terminate a long running transport request to re-import again ?

• Transport is not getting terminated. How to do terminate?

How to troubleshoot when a transport is running for unusually long duration and not getting completed or terminated ?

Go to transaction STMS_IMPORT and identify the transport which is running since a long duration.

In the below screenshot, transport with the truck symbol is the long running one

How to troubleshoot a background job running for long duration in sap?

How to troubleshoot a background job running for long duration in sap?

This article answers how to troubleshoot a background job running for a long duration

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

1) First of all identify the job that is long running and identify details like job class, workprocess that is executing the job

How to identify long running background jobs

2) Click on the job to view the display job screen. In the screen, click on job log to understand what is being performed by the job currently. This may give details like job is currently extracting some data packages or processing data packages etc

3) Identify the executing server and process id of the job from the step 1 and goto transaction SM50 of the respective executing server to view more details about the background job running.

Figure out the status of the job like On Hold or running from the process overview. If the job is On Hold, find out the reason for On Hold by examing the "Reason" column of SM50 transaction. Reason for On Hold could be due to CPIC/RFC/DEBUG/ENQ/PRIV/UPD etc.

Double click on the reason column for detailed information on the same and troubleshoot accordingly. If reason is RFC, check out which RFC it is referring to and cross check whether destination system is up or not and any other problems with that system.

• If it is ENQ, check out any lock issues like lock overflow etc
• If it is PRIV, check out for memory bottlenecks
• If it is UPD, check out whether any update issues
• If it is CPIC, check out for any network , gateway, message server and other communication problems

4) After performing step3, if you figure out job is not on Hold and it is in running state, then examine report column to identify what report/program is being executed by the job. Once you got the report/program details, figure whether it sap program or custom program and take actions accordingly.

5) Also examine Action and table columns in SM50 transaction of respective executing server to identify what is the action( roll in/roll out /Sequential read/Physical read/insert/update/delete etc)  being carried out by the job currently and what is the table on which action is being carried out.

If it is sequential read, figure out the cost of that sequential etc and consider for indexing etc. If it is physical read, check out whether there are too many swaps and consider resizing buffers accordingly. If you observed delay is due to high roll in/roll out, identify reasons for the same and tune buffer/memory parameters accordingly.

6) Once you get the table details on which action is being carried out, figure out        

•     How many records are existing in the table ?
•     Is this taking long time due to volume of records ?
•     Are there proper indexes on the table ?(If no proper index, consider index creation  by taking help of DBA )
•     Is the table having upto date statistics ? (If statistics are out of date,

              consider updating statistics of that table)

7) Consider debugging the process in SM50 ( Program/Session -> Program ->   Debugging ) to figureout the issue

8) Using ST05 or ST12, a trace can be taken for background job to figure out where exactly time is being consumed and to identify various cpu/memory bottlenecks or any buffer issues.

9) STAT/STAD transcation can be used to figure out what is the reason for high response time and actions can be taken accordingly

10) By taking help of ABAP er, even ABAP run time analysis can be done using SE30 transaction

By following the above steps, you can pin point the issue and take actions accordingly to minimize runtime of long running background jobs.