on 01-22-2016 2:55 AM
Dear SAP Gurus,
There is an unexpected increase in the background jobs with status "Scheduled". Everyday more than 300 of these jobs are coming under this status and the user is a System user. Also when I try to display these jobs through SM37 it throws me dump may be because of its huge quantity. Could you please provide your expertise here as to why is this happening.
Regards,
Abhishek Paritosh
+91 9860604735
Dear All,
Finally the issue is resolved. And the solution goes like this:-
Job SUBMIT_J_2GLPPDL_0820013449 will not appear any more in the system. The job mentioned is appearing from the main job A(name changed). If the delivery for which B(program name changed) is not in processed status for that the job gets scheduled always by the main job.
Thank you all for your support. Hope it remains the same always .
Regards,
Abhishek Paritosh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Firstly, the "Scheduled" status jobs can never start.
The job has either been descheduled(Released->Scheduled), (if it is this case, the original start condition is still visible), or it never had a start condition.
※ if user has no release privilege, The job stays in status "Scheduled" with start condition.
Object: S_BTCH_JOB
JOBACTION = RELE
please see the wiki:
Job Status Issue -- Troubleshooting - Application Server Infrastructure - SCN Wiki
This is also the root cause why you got error when click on to the job to look for the steps, I think.
Return to the main issue here, the jobs would not exist in sm37 unless there is a "process" create the job data into job tables.
regarding job tables, please refer to wiki:
Database Tables for Background Processing system - Application Server Infrastructure - SCN Wiki
I think you can try to find out the "process" by checking the following steps:
1, checking the SM37 or job main table TBTCO, find out the exactly timestamp when the jobs were created everyday
2, according to the job creation timestamp, checking the SM37 or job main table TBTCO again to try find out if there is a job running on the timestamp, trigger the more than 300 "Scheduled" jobs.
3, if there are no such jobs, probably, the jobs were created by third-party software via calling BAPIs.
you should check RZ15 log according to the job creation timestamp, try to find out the third-party software.
Thanks and best regards,
Shi Feng
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Column SDLDATE means "Date of job/step scheduling" which indicates the job first creation time.
here, in this case, you should check LASTCHDATE and LASTCHNAME because it is possible that the job has been exist in the system long time ago but was copied by one "process" every day....
Best regards,
Shi Feng
Hi,
The job has not been completely defined(probably the step definition is missing).
The job was defined with a call to the JOB_OPEN function module. But no job steps have been defined with the JOB_SUBMIT function module.
when the jobs were created into system everyday exactly ?
please check system log(sm21) if there are any error messages.
please also check if there are any third-party softwares be using to trigger jobs to your system.
Since incomplete jobs are useless, you can consider to delete these jobs by using the program RSBTCDEL2.
Best regards,
Shi Feng
Hi Abhishek,
Added to Feng..
Yes ,since the Job_Submit(to add a job step to a background job) function module ,start condition is not defined properly, that is the reason why the job is not released, eventhough the user had required authorization to release.
And also it seems like some one has created this job through tcode J2GLPPDL(Main program for printing deliveries) related to SD deliveries.
So if possible please get in touch with your SD consultant and understand what they actually do through tcode J2GLPPDL and then proceed further.
Best Regards,
Mervin Joseph
Hi Abhishek,
Message no. BT182
Suggest you to follow SAP KBA 1964073 - SolMan: Many jobs CCMS_CPH_RAW_DATA_UPDATE and CCMS_CPH_AGGR_DATA_UPDATE with status "sche...as the same is related with SAP Solution Manager,but it might be helpful for you in resolution.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It is possible that this is being spawned by a process on the system or from another system, check if there was any changes to the system recently if this a recent occurrence. Also if sm37 is dumping look in sm50 select a batch process and look at the logs to provide more information.
Regards,
Ryan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Fernandez,
I found the jobs from the table TBTCO and it seems there is some problem with the job definition. Because after I click on to the job to look for the steps and the config it throws me error :
Message no. BT182
The job that you have selected has not been completely defined. You therefore cannot modify the job's attributes. The job was defined with a call to the JOB_OPEN function module. But no job steps have been defined with the JOB_SUBMIT function module.
A possible explanation for this error is that a job was created non-interactively through the background programming interface. However, the program that created the job did not finish defining and scheduling the job.
Job attributes not modified.
Use the background job management facility to edit the job and finish scheduling it.
Regards.
Hi,
display these jobs through SM37 it throws me dump
Could you share the dump details from ST22 ?
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
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.