on 08-01-2014 7:29 AM
Hi Mijodrag,
If you have access to view the jobs in SM37 select them by clicking on the tick boxes on the left of the screen as per my attachment.
Otherwise you will have to identify via SM66 on which server the job is running, then via SM51 go to that server then to SM50 select the relevant processes and "Cancel without core" as per below attachment.
Once this is done someone will have to investigate why these jobs are running so long usually these jobs are not long running there might be some other problems on your system as well see SM21/ST22 perhaps as well.
Kind Regards,
Johan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mijodrag,
the job SAP_COLLECTOR_FOR_PERFMONITOR is the workload collector job, it starts reports from the table TCOLL. If this job is running to long, then most likely one of the reports in TCOLL table have problems and you have to find out, which report. For this you have to check SM50 what the corresponding work process is executing, you have to check the job log, if you see some hints there, and you have to check the list of started reports under ST03 --> Collector and Performance DB --> Performance Monitor Collector --> Log --> double click on the line with the latest time stamp. Here you will see the list with the started reports, most likely the report with the latest time stamp is hanging. To validate this you can execute this report manually in SE38, if it is really hanging. After you have found out the causing report you should search with this report in the SAP notes, if all corrections for this report are applied.
You can deschedule only the affected report from table TCOLL as a workaround until you find the reason, why this report has problems, and you do not need to deschedule the whole job.
Regards,
Alwina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
check the below link for more info:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/84/9e0e422dfcdc2ce10000000a1550b0/frameset.htm
Regards
Arun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Could you paste the job logs of any one active job, preferably the first active job?
Mostly the first job might have hung somewhere and is holding the resources for next schedule of jobs to remain in active state.
Also I could find job is running every hour. So if permits, you can cancel the active jobs and wait for the next run to check the status.
Regards,
Nikhil
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.