Killing a job in "Ready" Status

HI all,
Is there any way that I can delete or cancel a job which has a status "Ready"?
Thanx in advance.
Rgds
Lalit Rana

please only post your question in 1 forum.
I answered you at How to kill a job in "Ready" status.

Similar Messages

Source system jobs in ready status

Hi Gurus,
I am Extracting data from R/3 to BW, when i execute the infopackage the jobs in source system are in ready status and they are not moving to active & finished status.
Is there any method to make the jobs in source system active manually.
Thanks & Regards,
chinnu.

When you execute the infocpackage you must use the inmediatly option for execution or programmed job ...in your case is assume that you use the orogrammed job....if you use this last option...you must setup your job with init time...if you do not use the start time and hour the job will never starts....this could be your problem

Kill a job with status "Ready"

HI all,
Is there any way that I can delete or cancel a job which has a status "Ready"?
Thanx in advance.
Rgds
Lalit Rana

please only post your question in 1 forum.
I answered you at How to kill a job in "Ready" status.

Job to process messages in Ready Status in SMQ2 ECC

Hello friends,
I am sending out messages from SAP ECC to PI using proxy . The messages are getting stuck in SMQ2 in READY status. I have to each time manually go and activate the queue to send the message out of SAP ECC.
Is there any job to process them automatically that needs to be set up in SAP ECC ?
Thank you,
Teresa

Hi,
Investigate why messages were strucked in Queues, there could be some reason, i suggest you too deregister and register queues once again.
if possible assign sepprate queue for proxy interface.
Regards,
Raj

Backgroung jobs remain in "Ready" status

Dear All,
Our Production is one central instance ( on Hp-ux ) and 3 application server ( one is on Hp-ux work as application server/failover server when central server down then that server act as central server ( cluster ) . and two more application server on redhat enterprise server 3).
Problem is that when my Linux application server in working or started or functioning background jobs (mostly) remain in ready status why?
In same forum I read that after restart system it will finish but it is not a solution.
Please guide me
Regards
Rayyan

check whether you have enough free bgd processes on second node?
And check those jobs are not server specific...
Regards,
Nick Loy

Queues in READY status for no apparent reason

Dear All,
This question has been posted many times but never saw a conclusive answer on this forum.
To repeat, I see queues being built in READY status in APO inbound for no apparent reason.
All settings of scheduler being fine (SMQS - Type R), there are large number of queues awaiting to be manually unlocked from READY status and they get cleared on unlock. There are no waiting queues but still entries in say an update of a stock queue are like 70+. I am able to clear them manually but that would be stupidity when I am talking of 30K queues build up thus.
Its not that not a single queue is moving. Some are getting processed (RUNNING) on their own but thats at snails speed as compared to the queues in READY.
I have scheduled the report /SAPAPO/RCIFRESTART that seems to have scheuled something in the background but I cant trace that job.
Please help.
Regards,
Loknath

Loknath,
If you have 'many' queues 'RUNNING' for a long period of time, LUWs that are inline behind them will eventually stop trying. You can restart these queues with the /SAPAPO/RCIFRESTART program mentioned above.
There are lots of ways to tune queues to meet business requirements. Speak to your local CIF expert.
Some people use a job to run /SAPAPO/RCIFRESTART on a regular schedule. I have seen a system where this job is scheduled to run hourly.
30K queues is not really reasonable. If you always have this backlog, then there is a performance issue that needs to be addressed (SCM is not able to process the data as fast as ECC is sending). If this is a startup, then you just have to be patient. Initial loads can sometimes take days to fully clear all queues, especially if the SCM is sized a bit on the small side. Continue restarting until you have cleared all queues, then see if they begin to build again.
Best Regards,
DB49

Queues in READY status

Dear All,
This question has been posted many times but never saw a conclusive answer on this forum.
To repeat, all settings of scheduler being fine (SMQS - Type R), there are large number of queues awaiting to be manually unlocked from READY status to clear them. There are no waiting queues but still entries in say an update of a stock queue are like 70+ in READY status. I am able to clear them manually but that would be stupidity when I am talking of 30K queues build up thus in READY status. Its not that not a single queue is moving. Some are getting processed (RUNNING) on their own but thats insignificant as compared to the queues in READY and also pathetically time consuming.
I have scheduled the report /SAPAPO/RCIFRESTART that seems to have scheuled something in the background but I cant trace that job.
Please help.
Regards,
Loknath

Loknath,
If you have 'many' queues 'RUNNING' for a long period of time, LUWs that are inline behind them will eventually stop trying. You can restart these queues with the /SAPAPO/RCIFRESTART program mentioned above.
There are lots of ways to tune queues to meet business requirements. Speak to your local CIF expert.
Some people use a job to run /SAPAPO/RCIFRESTART on a regular schedule. I have seen a system where this job is scheduled to run hourly.
30K queues is not really reasonable. If you always have this backlog, then there is a performance issue that needs to be addressed (SCM is not able to process the data as fast as ECC is sending). If this is a startup, then you just have to be patient. Initial loads can sometimes take days to fully clear all queues, especially if the SCM is sized a bit on the small side. Continue restarting until you have cleared all queues, then see if they begin to build again.
Best Regards,
DB49

Outbound queues are in ready status

Hi,
In our system outbound queue are getting stuck in READY status. They are not getting executed automtically from READY status we have to manually exceute them in SMQ2.
How i can clear the queue which are in READY status.
Thanks & Regards,
Koushal Solanki

Hi,
Please check if there is any standard background job available to schedule it to run for every 5 or 10 minutes so that it will check the queues with Ready status and then execute them automatically. Also, check the reasons why jobs are coming to Ready status.
Regards,
Sharath

How to kill a job in SM37

hi All,
can someone wxplain me how to kill a job in SM37 which is delaed by 10,000 secs.
cheers

Hi Rase,
goto SM37 and click on the active selection and enter the jobname and then click excute the particulr job should appear highlight the jobname then click on the stop iconthat appears on the taskbar( 3 rd from left)
or goto SM50 Click on the process and select process->stop without core
or
set a running infopack of the chain (in RSMO) to red, thats will stop the chain (if there are no parallels, else set all parallels to red).
****Assign Points If Helpful****
Regards,
Ravikanth

Can I set up a job that kills multiple jobs?

So, I've got some jobs that access a remote DB, and the link is not terribly reliable. When it hiccups, if a job is running, it hangs forever. Using this forum, I was able to set up a job that is triggered when a job goes over max duration, and it simply kills and restarts the job, it works great for the one job that typically runs long enough to get hit on a daily basis. This morning, I noticed one of the other jobs hung. So, I realize I can easily set up another kill job that gets fired off when this other job hangs, but what I'd really like to do is have one master kill job that can be used to kill any of several jobs so I don't have to have a kill job for each job that might get hung.
Is there a way to reference, in the PL/SQL block, any of the "tab" fields used in the condition block? I'd like to check tab.user_data.object_name in the PL/SQL block and kill/restart the appropriate job. So, my condition would be a generic event_type of JOB_OVER_MAX_DUR and would fire for any job meeting that condition. Possible? Feasible? Dangerous?

Thanks for the reply, Tom.
I am using version 10.2.0.4.
Point of clarification: I don't want to kill multiple jobs on one execution. I just want to write one job that can handle killing any one of the several jobs that I'm having issues with. So, for example, I have jobs A, B, and C. I want one snipe job that is generically called when anything raises a job_over_max_duration event, and it would figure out which job (A,B, or C) that is stuck and kill it.
From your reply, it sounds like I could do this in 11g, but probably not in 10g?
Thanks again!
---dale

Hi i have 50 infoobjects as part of my aggregates and in that 10 infoobjects have received changes in masterdata.so in my process chain the Attribute change run in running for a long time.can i kill the job and repeat the same.

Hi i have 50 infoobjects as part of my aggregates and in that 10 infoobjects have received changes in masterdata.so in my process chain the Attribute change run in running for a long time.can i kill the job and repeat the same.

Hi,
I believe this would be your Prod system, so don't just cancel it but look at the job log. If it is still processing then don't kill it and wait for the change run to complete but if you can see that nothing is happening and it is stuck for a long time then you can go ahead and cancel it.
But please be sure, as these kind of jobs can create problems if you cancel them in the middle of a job.
Regards,
Arminder Singh

Messages stuck in Inbound Queue with Ready Status

Hi All,
The messages in the Inbound queue are getting stuck in Ready status.
I have to manually Unlock each queue to start the processing.
After some time again all the message queue are back to the Ready State.
Please help me on this issue.
Regards
Milan

go to --> sxmb_adm
Manage Queue
Select all Queues, Activate Queues.
& check your scenarios, now it will not stuck due to this error.

Task in "Ready" status always, when tested in SWUS

Hi - Hv created a very simple task - it has a BOR/Method which gets a PR No and passes back some PR related fields back to the task. An agent has been assigned with my user id. SWU_OBUF has also been tried. I am on ECC 6.0 and looks like all authorizations are good. But when executed in SWUS, this task remains in ready status & no Inbox/Outbox item appears in SBWP.
The log says the work item is a Dialog step but the BOR/Method attributes are NO DIALOG. 'Am at my wits end. Any help? Thanks!
One update : Authorizations in client 100 are set. When tested in 100 status is completed. When tested in client 200, status is ready. Can't do a SU53. How can I tell BASIS which authorization is missing, if any?
Regards,
Shireesh M
Message was edited by: Shireesh M
Shireesh Mitragotri

Hi,
as you pointed out, this could be an authorization issue, also check if you're not forgetting user parameters.
If I were you i would bother someone to include su53 in your profile since this is clearly needed to explain/exclude the behaviour of the wf.
Kind regards, Rob Dielemans

BI_PROCESS_TRIGGER event job in released status ONLY

HI ALL,
I WANT TO TRIGGAR PC TWICE IN DAY 5 PM AND 2AM.
1.I CTEATED EVENT IN SM62 (ZSDPC_EVENT)
2.I CTEATED SE 38 PROGRAM (zsdpp_pc_event_program )LIKE BELOW
REPORT zsdpp_pc_event_program.
DATA: gv_time TYPE sy-uzeit,
      eventid TYPE btceventid.
gv_time = sy-uzeit.
eventid = 'ZSDPC_EVENT'.
IF ( gv_time GE '170000' AND gv_time LE '170000' )
   OR ( gv_time EQ '020000' AND gv_time LE '200000' ).
CALL METHOD cl_batch_event=>raise
    EXPORTING
      i_eventid                      = eventid
    EXCEPTIONS
      excpt_raise_failed             = 1
      excpt_server_accepts_no_events = 2
      excpt_raise_forbidden          = 3
      excpt_unknown_event            = 4
      excpt_no_authority             = 5
      OTHERS                         = 6.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDIF.
3.I SPECIFIED AFTER EVENT IN MANAIN VARIANT .ACTIVATED AND SCHEDULED PC
4. THEN RUNE THIS PRORGAM IN SM36
BUT MY PROBLEM IS IN SM37 JOB BI_PROCESS_TRIGGER event job in released status ONLY
please guide me if i am wrong .
REGARDS,
KP

It is supposed to be in Released status.
The BI_PROCESS_TRIGGER job is scheduled to run based upon the event being triggered (from your ABAP program). The only thing this job does is trigger the event that runs the next process in your process chain. If you set up the Start variant in your PC to schedule "After Event" and you set the periodic flag, then after the BI_PROCESS_TRIGGER job finishes, it will reschedule itself. So, there will always be a BI_PROCESS_TRIGGER job in a Released status.
Again, the BI_PROCESS_TRIGGER job does not run the entire chain. It only triggers the next processes in your chain.
Does this help?
PS. Are there any BI_PROCESS_TRIGGER jobs in a Complete status? If not, then there is an issue with your ABAP program.
Edited by: Geo on May 4, 2009 11:13 AM

Export message in READY status before oaiimport

Hi all,
We do not use migrate for production environment but OAIIMPORT as :
- oaiimport is more reliable
- we don't want to let production people doing those manipulations with ISTUDIO
But we have a problem as we begin to have a lot of flows on production (and around 10 running adapters ) :
IF a message stay in the ready status in the OAI_HUB_QUEUE we do not want to loose this message (The oaiimport drop the whole queue)
Question : is it possible to do a normal export of the oai_hub_queue before the oaiimport so as import this queue after the oaiimport ?
Does someone as the same issue ?
regards

Hello,
The problem was i think that we used these parameters (for DB adapters) :
agent_pipeline_from_hub=false
agent_pipeline_to_hub=false
The effect of these parameters is to suppress file persistence which is "more secure" as database persistence is more reliable (cluster node)
But the main drawback is that the oaiexport/oaiimport method for upgrading production repository is no more safely usable as explained in the first message.
We will desactivate these parameters.
Thank you,
Olivier

Killing a job in "Ready" Status

Similar Messages

Maybe you are looking for