on 06-10-2007 2:11 PM
Hello experts,
I have a job that sometimes runs for about 13 hours.
Yesterday, we had make some updates in the function module that is called from the job, and the job yesterday rans for more than 20 years; as theb job must start every day at the same hour, I had interrupt it and I had restore the function module with the old version (because I think that the updates have cause a worsening of performance).
But today I have again the same problem (run for more than estimated hours).
In SM21 I see this error:
Transaction Canceled BT 513 --> the log advises:
&CAUSE&
When a job is created, a "latest start date" can be specified in
addition to the regular start date. When the "latest" date is
specified, the job will not be started regularly after that date.
This message means that this exact case applies. Due to a system
shutdown, fully occupied work processes, or some other reason, this
job was selected for execution after its latest start date was
exceeded.
&SYSTEM_RESPONSE&
The job that has exceeded its latest start date is not started normally
or executed. Instead, it is set to status "Cancelled", and this
message is recorded in the job log.
If this job has successor jobs, they will be started afterwards. The
system responds as if the job were cancelled due to error.
&WHAT_TO_DO&
This problem can have several causes, each with its appropriate
reaction:
The planned start date and latest start date are too close, which
increases the probability that the latest start date will be exceeded.
To correct this, select a later "latest start date".
Long-running jobs were processed before this job. These jobs occupied
all the available work proceses at the planned start date and are not
completed until after the "latest start date" of the scheduled job. In
this case, you can either increase the number of work processes or
change the job sequence for a more favorable processing run. Of
course, you can also select a later "latest start date".
A third possible cause of this problem could be a system shutdown or
breakdown. Of course, except for planned downtimes, there is little
you can do to influence this. Accordingly, there is little you can to
do avoid it, as well.
Someone think that my problem is related to this error message?
How I can solve the problem?
Or, have you got some ideas?
Please it is urgent.
Thanks in advance,
Vito
Hi Vito,
Yes, I think your problem is related with this.
Have you read the error message that you have pasted here yourself.
Also can you please tell me who has scheduled this job I mean yourself or some other consultant.
The probable causes of your error are :
1. You have not specified the "latest start by date" and "latest start by time"
-
> Many times it happens if too many background jobs are running at the same time which occupies all background work processes and no work process is left to process the job. In that case if you have specified the latest start date and time then system checks for availability of free work process until the specified time limit is not crossed. That means if the specified time has passed then the job will not start.
2. In your case first check the time at which the job is scheduled.
Crosscheck it with your offline backup time. How long does your offline backup run. if both timings clash, then schedule the time accordingly taking into consideration of the time taken by your job to run.
3. Also check how many jobs ( especially long running )are running at the same time. Normally short period jobs will not harm your schedule as you will definitely get some process to process your job within 5 minutes.
4. To change the job schedule select the job in transaction sm37 ( the one which has status : Released )
Then in the Menu Bar Job-> click on releasedscheduled
Now the status of the job will be scheduled.
Now click on the job ( showing status : scheduled )
Goto Job---> change
And now set your new time with latest changed by time.
And now check how much time does it take.
I hope this will solve your problem.
Please confirm and award accordingly if solved.
Cheers.
-
Shamish
Message was edited by:
Shamish Lele
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.