on 12-21-2015 9:00 AM
Hi Praveen,
Many reason will be there.
Now work processes looks fine.
You can get error and time stamp from work directory. You can trace the log file dev_w2.
Work Directory: /usr/sap/SID/<Instance Directory>/work
Here red 1 in the ERR column denotes the number times which that WP has been terminated or restarted.
You do not need to do anything action. When you stop and start SAP it will disappear.
Regards,
V Srinivasan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Praveen,
You don't need to worry about this error. The "Failure" status indicates how many time a workprocess has failed since the instance was started.A workprocess can be terminated for various reason, eg. due to an program error or can be terminated by an administrator.
The termination counter can be reset from tcode sm50>>List>>reset>>failure
The above step will reset the termination and the red color will disappear.
I believe you are one of my kind who dont wanna see any red status in the system
Best Regards,
Mervin Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Praveen,
The "restart after error" option configures SAP to restart or not the work process after an error.
If set to "no", the work processes that face an error will remain in "stop" status.
When using the default setting ("yes"), the work process restarts automatically after an error, coming back to normal operation.
The only way to remove that red counter is to restart SAP, as far as I know.
The PID you see at the beginning of the dev_w2 is different exactly because the work process has restarted after the error. Search the dev_w2 for the current PID.
You should reach a point where the work process has restarted.
Analyzing the trace entries before the new PID should reveal what happened.
In case the work process has restarted more than once, the reason for each restart might have been different.
You can then search for the system ID ("SID") to find each of the restarts.
As you will notice, the same header from the beginning of the trace is also written every time the work process restarts.
Regards,
Isaías
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Praveen,
In the error field you can see 1 , it means that the work process was aborted for one time.
The number in that column indicates that how many times the WP got terminated/aborted. Don't kill the work process.
There many be many reasons for WP termination,
- Like Lack of memory to execute the report/job.
- Might be a network issue Etc.
Please review this link so that you will have a better idea - SM50 - Process Overview - Basis Corner - SCN Wiki
and Error doesn't affect your system performance. If it is a Non-Prod please schedule a system bounce on regular basis for better performance.
Please reward if this is helpful.
Thanks and regards,
Saikiran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Praveen,
Try this
SM66 Systemwide Work Process Overview
Global workprocess is very usefull when we have more than 1 DI this will show all WP (CI,DI) WP status
look for all WP processes and observe error (red) or in stale state,
We can also display only stop process goto => process list => select process => check status
Restart the stop process by going to stop wp app server (sm50) => select wp => process => Restart after error => yes
Regards,
V Srinivasan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This error can be an old one.
If you want to rectify error, you can check the dev_w2 ( here work process is 2 ) file in the instance work directory. Error may be an old one.
If you want to not see this 1 here, you can create a fresh log dev_w2 .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, you can find the details in developer work trace (transaction ST11 choose your dev_w<num> trace file.)
Regards,
Anatoliy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.