Long Delay Release Background Job

Dear Expert
We now use BI Netweaver 2004
many times background jobs have release status in long time,
so the jobs can not be active
if I change priority to A, the jobs can be active
Why I must change priority the job for active ?
How to solve this problem ?
really appreciate your help
Regards
Jeiming

1) See it in SM50 whether how many BGD processes are available (Status: Waiting) at the time of 'Release' job is waiting.
2) Suppose if you find more processes are in waiting status then check with your basis team to understand how many are available for priority A and remaining.
3) If you don't find many BGD processes then your job is waiting for availability of BGD process.
Thanks
Viswa

Similar Messages

Report to cancel released background jobs

Hi Folks,
Can anyone guide me whether there is any standard report/program where i can delete/cancel the background jobs already released/scheduled? We can cancel individual job using SM37, but i need to cancel "n" number of jobs at one slot.
Thanks in advance.
Regards,
Shiva

Siva,
can plz tell me how to change or reschedule the time on background job ?
Dilip

Delay in background jobs..Need some info

Hi experts,
We have a background job scheduled for every 2 hours in our system.But this job is going to delay state intermittently and not getting triggered at the right time.Could anyone tell the reason for the same and let me know the transactions I have to look in .
Regards,
Srikanth.

>
Thomas Zloch wrote:
> Oh I thought you were picking on me, so I picked back. Never mind if I got that one wrong
> Thomas
No pickiness intended. I simply meant that there may be some authorization issues with changing the priority of a job. But basis should be able to do it.
Rob

Delay in background job

Hi friends,
I have to schedule a back ground job in user-exit , that to i have to give 30 sec delay how i can i get it.
thanks and regards,
Jyoti.

DATA: job LIKE tbtcjob-jobname,
      jobcount LIKE tbtcjob-jobcount.
CLEAR: job,jobcount.
    job = 'ZBACK_MB1B'.
    JOBCOUNT = '14310400'.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
    jobname                = JOB
IMPORTING
   JOBCOUNT               = JOBCOUNT
CHANGING
RET                    =
EXCEPTIONS
OTHERS                 = 4
DATA: authcknam LIKE tbtcjob-authcknam.
CLEAR: authcknam.
authcknam = sy-uname.
*params-primm = space.
CALL FUNCTION 'JOB_SUBMIT'
EXPORTING
ARCPARAMS                         =
   authcknam                         = AUTHCKNAM
    jobcount                          = JOBCOUNT
    jobname                           = JOB
LANGUAGE                          = SY-LANGU
PRIPARAMS                         = ' '
   REPORT                            = 'ZMSKA_JOB'.
DATA: sdlstrttm TYPE tbtcjob-sdlstrttm,
released LIKE btch0000-char1,
p_job_start_date type sy-datum.
sdlstrttm = sy-datum + 150.
sdlstrttm = sy-uzeit + 150.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
    jobcount                          = JOBCOUNT
    jobname                           = JOB
   SDLSTRTDT                         = p_job_start_date
   SDLSTRTTM                         = sdlstrttm
IMPORTING
JOB_WAS_RELEASED                  = RELEASED.
Is this correct plz check it out

Long time for execution for scheduled CIF background jobs

Hi,
we hv schedlued CIF background job to be run daily around 10.30 PST.
there is large variation for the time required for execution of this job.
on 26 Dec, it took approx 48000 seconds while regular average is 120 seconds only.
today, despite past of 6000 seconds, the job is still in ACTIVE stage.
can anyone know why such long delay for such jobs?
how can i reduce its execution time (as one of case in a week)?
rgds/Jay

Hi Jay,
A few obvious things to look for:
1. Multiple CIF activation jobs running at the same time
2. Large change in the master data, eg new plant, new Material Masters, new customers, etc etc.
3. Conflicts with other non CIF programs that may be going after the same data
4. Communication degradation between the OLTP and SCM clients
Normally you refer such questions to someone on your Basis team, or perhaps your DBA. They can turn on tracing tools that can track the changes in your environment that may be contributing to the changes in run time.
Regards,
DB49

Protecting a background job...

Hello!
   This question may seem ridiculous, but I actually have an application for it. Does anyone know if I can protect a released background job from being deleted (accidentally or intentionally), and if I can protect it from being cancelled while it is running?
Thanks!
John

Hi Rich;
   Unfortunately, that is not an option in these cases. We are running an event-driven job to track any instances of super-user log-ons in the system. The job checks to see if the super user has logged off, then it sends an e-mail of the transactions they executed to the big wigs. Since the super users have SAP_ALL, and they would need SM37 for other reasons, that probably will not work.
   It is a ridiculous question, and I can't imagine SAP would offer a solution but I thought I would try...
Thanks!
John

Background job delay due to 'ARFC' jobs running continously

Dear all,
As we are facing problem that,there is job starting with the 'ARFC'(example: ARFC:AC1F0C0D386B463CA88E8D10) which runs with all the users in the system.Thus the other background jobs even the sys monitoring jobs also goes for the delay for the longer time.This is happening from past 10 days.I m unable to trace what has got change in the system due to which ,I m facing this issue.I had checked in the job logs also, in which i didnt got any help.In that it is only mentioned owner of the job.Pls check this at the high priority as it is affecting my normal background jobs.
Thanks in advance.
Regards,
Akif

Hi akif,
jobs which are stuck at ARFC mode needs to trigger other event controlled jobs. since they are updating the Database, unless those jobs trigger this job cannot run forward so try to find what kind of jobs from the user who scheduled the job and then take the action if the jobs are related to support packages and releasing of change request then try to schedule RDD* jobs under user DDIC in 000 client
this is not due to instance consistency
regards,
kanthi

Background Job running long time.

Hello All,
One of customer background job running for long time more than 11 hours, but usually this jobs get completed within 4 hrs.
I have checked in WP trace file, it shows "WP has reached abap/heaplimit=40000000".
This is the Value I can see in RZ11. Now it is not possible to change the value.
Frequently facing this problem, please guide me to solve this issue.
Regards
Vinay.

Hi
First of all, abap/heaplimit is the limit of memory usage by a WP.
Follwing is the documentation from help.sap.com
The value of the parameter should be between 10000000 (10 MB) and 2000000000 (2GB), the recommended default setting is 40000000 (40 MB).
The objective is to have the least number of work process restarts as possible, without a swap space bottleneck occurring. The heap memory allocated by the work processes has to be released again.
As shown in the graphic, the value of abap/heaplimit should be smaller than abap/heap_area_dia or abap/heap_area_nondia, so that the dialog step that is running can still be executed. This prevents the work process from working against the operating systemu2019s swap space limit if there is a programmed termination of the work process.
So,Do the above checks. And importantly check the memory utilizations at the time of running your job and check whether any other job was also running at the sametime.
Increasing the parametes is not a good idea.. If you continuously face this issue then only think of parametes. As u said ,this problem is not happenng too often.
Hope this is useful

Background job status "Released"

Hi ,
I am executing standard SAP program in background and it shows the status as "Released" with "Delay" more than 3000 sec.
What is the reason I am not able to start the job with "Active" status?
Please help.
thanks & regards,
Yogita

>
Rob Burbank wrote:
> If it wre already running, the status would be active.
Rob,
Yes,Its really depends on how "Background job cofiguration" has been done in system by basis.
As i can also see the job status is only Realesed(Not active) once i ran it in background immidiately.
And once job finished it shows "Finished" status.No where "Active" status came
@Yogita:Your job is still running i guess since more than 3000Sec.so thats why it(Time) is showing in delay.
Once job is finished you will be able to see its status Finished.
I would also suggest you to Knock basis
Cheers,
Amit.

Background job running for a long time - trace is not capturing.

hi guys,
My background job runs for more thatn 4 hours. some times. (normally it completes withing one hour)
i tried to trace using st12 ....and executed this program. but not got complete trace report of 4 hours.
what is the best way to trace long running programs like this.
is there any alternative for this...???
regards
girish

Giri,
There is no need to trace a program for the full 4 hours. There is usually just one piece of rogue code causing the problem, and it can be identified quite quickly.
If I were you I would just watch the job run via SM50, to see if it lingers on any database tables. Also check if the memory is filling up - this is the sign of a memory leak.
You can also try stopping the program (via SM50 debugging) at random points, to see what piece of code it is stuck in.
The issue should reveal itself fairly quickly.
Tell us what you find!
cheers
Paul

Background job is running for long tome in source system (ECC)

Hi All,
Background job is running for long tome in source system (ECC) while extracting data to PSA.
I checked in ECC system SM66,SM50 the job is still running
in SM37 the job is Active
There are only maximum 7000 records the extractor is 2LIS_02_ITM but it is taking 11 to 13 hours to load to PSA daily
I had checked enhancements every thing is correct.
Please help me on this how can I solve this issue.
Regards
Supraja K

Hi sudhi,
The difference between Call customer enhancement... and Result of customer enhancement:... is very less we can say this as a second.
The difference is between LUWs confirmed and 1 LUWs -
   and Call customer enhancement -
Please find the job log details below, and give me the solution to ressolve this
01:06:43 ***01:06:43 * ztta/roll_extension........... 2000000000                              *                 R8           050
                 R8           048
01:06:43 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA     RSQU          036
06:56:31 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 5.208 records                  R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5.208 records                      R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 PSA=1 USING SMQS SCHEDULER / IF [tRFC=ON] STARTING qRFC ELSE STARTING SAPI                 R3           299
06:56:31 Synchronous send of data package 1 (0 parallel tasks)                                      R3           410
06:56:32 tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =                           R3           038
06:56:32 tRFC: Start = 00.00.0000 00:00:00, End = 00.00.0000 00:00:00                               R3           039
06:56:32 Synchronized transmission of info IDoc 3 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 3, IDoc No. 1549822, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Altogether, 0 records were filtered out through selection conditions                      RSQU          037
06:56:32 Synchronized transmission of info IDoc 4 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 4, IDoc No. 1549823, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Job finished                                                                               00           517
Regards
Supraja

Alert monitor for long running background jobs

Hello,
I have to configure an alert moniter for long running background jobs which are running more than 20000 secs using rule based. I have created a rule based MTE and assigend MTE class CCMS_GET_MTE_BY_CLASS to virtual node but i dont find a node to specify the time.
could any one guide me how can i do this.
Thanks,
Kasi

Hi *,
I think the missing bit is where to set the maximum runtime. The runtime is set in the collection method and not the MTE class.
process: rz20 --> SAP CCMS Technical Expert Monitors --> All Contexts on local application server --> background --> long-running jobs. Click on 'Jobs over Runtime Limits' then properties, click the methods tab then double click 'CCMS_LONGRUNNING_JOB_COLLECT', in the parameters tab you can then set the maximum runtime.
If you need to monitor specific jobs, follow the process (http://help.sap.com/saphelp_nw70/helpdata/en/1d/ab3207b610e3408fff44d6b1de15e6/content.htm) to create the rule based monitor, then follow this process to set the runtime.
Hope this helps.
Regards,
Riyaan.
Edited by: Riyaan Mahri on Oct 22, 2009 5:07 PM
Edited by: Riyaan Mahri on Oct 22, 2009 5:08 PM

Background job in Released status and does not run. What is the problem?

Hi Experts,
I ran a ABAP report as a background job. But when I see the job status in SM37 I found that it is "Released" but the job does not run further, It remains in "Released" state. I have given the correct variant and start condition "immediate" . Moreover there is no spool and log as well.
The ABAP report runs fine in forground. It used to run in background few days back.
What could be the problem? Kindly help!
Thanks
Gopal

Hi Bob,
But I checked after 2 days still the job status is in Released state. There were some other jobs that ran successfully. So atleast after two days I hope the job should have run. I can't even delete it. What shall I do?
Thanks
Gopal

Background job delay

Hi Experts,
I have a problem. When saving production order, I need to schedule job, which runs 5 seconds after current time and changes some fields in production order.
Problem is, that this job is alwayse delayed. Sometimes it is only 10 seconds, sometimes one minute.
Can I ensure to start job in planned time without delay?
Thanks&regards,
Jirka

Hi Jirka,
While we configure the background job scheduling you must have given immediate start.Am I correct.When we specify it means that the action reaction is quick immediately.We know that the process execution within SAP is so vast that the process has to wait for a bit of time that is what the cause of the delay you can check while the process you trying to achieve in the mean time you can check SM51 or SM 50 both youo can see that the delay is just because of the work processor availabilty.To improve the performance of the process please do contact the basis team.
Hope your query resolves.
Have a best day ahead.

Background Job RSPPFPROCESS Taking too long to execute.

Hi Gurus,
I'm working with SAP CRM 2007 - Interaction Centre
We have configured first response date and to do by date in item category.
If agent fails to response within the first response date or if agent fails to complete
to close the ticket within the to do by date,An action is configured to trigger and an
escalation email(Smart Form) is sent to agent`s manager inbox.
We have scheduled background job for the program RSPPFPROCESS with variant in background
to trigger this actions( It is scheduled 4 times in a day ).
Previously this job used to take 6 hours to complete execution.
But now its taking 12 hours to complete the execution and there is no change in the
variant.
Can anyone please advice me reason for this behavior.
Kind Regards,
Vinod

Hi Manfred,
We are experiencing similar performance issue when running the RSPPFPROCESS Job. We opened a OSS message for quite some time but didn't get any useful help from SAP.
Can you please provide more information regarding your ZRSPPFPROCESS program on identifying the crtical performance steps to resolve the performance issue? We are also thinking of archiving the record in table PPFTTRIGG , we have over 73+ millions records in the table but there is no archiving object for PPF actions. We would like to focus on reducing the number of entries in the table PPFTTRIGG hopefully to improve the performance. Any thoughts on it?
Thanks in advance for your kind help!
Best Regards,
Madeline

Long Delay Release Background Job

Similar Messages

Maybe you are looking for