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

Similar Messages

Jobs Scheduled But Never Run or EM jobs remain in 'running' status

Hi All,
Please I need help on this: I have job scheduled through Oracle Enterprise Manager (OEM) but each time our Windows server is shutdown for patches update the job I scheduled failed and in the status column it shows that the job is still running ( Note: I do know how to stop/delete this job) BUT I will like to know if there's anything I need to do so that each time our server is shutdown the scheduled job will not fail to run.
Thanks
Wale

Jobs Scheduled But Never Run or EM jobs remain in 'running' status what is the output of user_jobs and user_jobs_running views when this happens? especially last_date, last_sec, failures, broken columns.

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

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

Jobs remain in status SCHEDULED

Hi all,
does anyone have an idea what to do when scheduled jobs which should run remain in status SCHEDULED instead of changing into RUNNING? The transaction run if started manually in the workbench.
I will restart MII but hoping to find another way to get the scheduler working. The system is MII 12.0.2.
Michael

Hi Nick,
thanks for your reply.
Actually the save "trick" is the one that mostly cures those problems, but not in my case. The status is correctly set to PENDING after saving the job, but when started again, the job got stuck in status SCHEDULED instead of RUNNING. When I try to run the job directly from the Schedule Editor, it says it has run, but actually it didn't.
I have also tried to stop and start the scheduler, but no change.
Michael

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

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.

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

PSA load remains in yellow status.

Hi Gurus,
I have created a generic datasource based on function module.
I have replicated the datasource in SAP BI dev instance.
I have even checked the extractor checker in R/3 and it shows 381 records.
On BI side I am loading data upto PSA.When I execute the infopackage for full load in the monitor screen I could see
"381 out of 0 records".The request remains in yellow status.
The idoc status in source system side is 03 and on BI side is 53.
I dont get any error message.Even I am not seeing idocs with red status in SM58 tcode.No logs are seen in sm21.
I even asked the basis team to check for RFC connection SM59 and partner profile.Every thing looks fine .
This loading issue is only happening with this specific datasource(ie datasource created on function module).
For other datasources load are carried out fine.
Has anybody faced a similar issue?.Please help in this regard.

seems the load is hung bcoz of thehung IDOCs.
Process the idocs manually. after
check the below things
--> Check weather the source system job finished or not?
If the job is finished check the TRFCs are processed or not?
In the monitor screen - menu bar --environment -->job overview (to check the job) -->TRFcs - to check the TRFCs.
Check for short dumps using transaction ST22.
-->Check for the Idocs in BD87 and if there are any IDOCs got stuck process them manually.
To process Idocs first change the status of request to red and try to process them in the background.

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

Documents remain in GenWWW status and conversion error message says success

Hi,
I have instaled UCM 11.1.1.4 and the situation is that documents remains in GenWWW status, the
conversion error message says success . In Ibr logs says everything went perfect, in UCM logs isn't recorded any error.
Anyone have a clue to solve this problem?
Update:
When runnig IdcAnalyse appears the following error:
./IdcAnalyze -filesystem
FileSystemFileStore:1.0.0.0 started.
Content Management System Server. Version 11gR1-11.1.1.4.0-idcprod1-101229T001824
Copyright (C) 1996-2011, Oracle and/or its affiliates. All rights reserved.
Analyzing filesystem...
.....................Error checking filesystem: Unable to locate extension for rendition flag 'L'.
Is this error related with the documents remain in GenWWW?
Thanks
Edited by: carlos.pereira on Jul 26, 2011 4:58 PM
Edited by: carlos.pereira on Jul 26, 2011 5:00 PM

Usually this issue is seen when the IBR's cannot keep up with the load and after a defined amount of time, the refineryjobs entries are cleared while the IBR's might still hold this content item.
If you do what Srinath proposes the refinery jobs is cleared as well as the queues on the IBR. This will not fix the issue with the documents in GenWWW, but it will make the way clear for (new) documents to be (Re-)submitted for conversion. IdcAnalyze should then be able to create a IdcCommand file with resubmit_for_conversion calls for all the documents in GenWWW state. Running this IdcCommand file should then convert all the documents that were "stuck" in GenWWW.

Risk Analysis Batch Job Stuck in Ready State

Hi,
I am not able to schedule Risk Analysis Batch job in RAR.The job is getting stuck on READY state(for unlimited period) and not performing any actions.
Nothing is displayed under job history or job logs with job ID.I have check background job demaon ,connectors and other miscell. options but not abl to find any clue.
Even i am executing risk analysis for single user,it's not happening.
Rgds,
Mukesh

For your problem, of job not getting schedule....it seems Deamon is not running.
To delete status of job which are in hung status
change VIRSA_CC_SCHEDULER job id should with status five will show job aborted.
are you using connection type 'Adaptive RFC', don't use it, use SAP JCO.
and restart your GRC box.
Regards,
Surpreet
please do check backend system, for VIRSANH is installed or not.
Edited by: Surpreet Singh Bal on Jan 28, 2011 10:32 AM

CCMS Autoreaction remains in READY - anyone knows why?

Guys, My autoreaction in CCMS remains in READY but it never runs.
Is there a job that is supposed to be scheduled to process them?
Any help is greatly appreciated.
Leonardo De Araujo

Hello Leonardo
Plesae check the pdf :
www30.sap.com/korea/services/pdf/4_Solution%20Monitoring.pdf
Regards ,
Santosh Karadkar

User Profile Service - User Profile Incremental Synchronization Timer job stuck at 33% Status: Pausing

User Profile Service - User Profile Incremental Synchronization Progress: 33% Status: Pausing
It has been almost 15 days.
Both User Profile Service and User Profile Synchronization Service are in Started state and FIM service also starting
I tried clearing sharePoint config cache.
I also restarted the sharepoint timer service.
I tried almost everything that is on Internet but nothing helped me.
Is there any other way to solve the issue as I was struck on production server (ASAP)
In synchronization serivce manager status of MOSS_DeltaImport is Inprogress from past 2 days
Best Regards.

Hi,
Please follow the steps in the link below to clear the configuration cache.
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
Here is a similar thread for your reference:
https://social.technet.microsoft.com/Forums/en-US/beaa852c-6f40-428a-b97c-20722864e045/user-profile-service-user-profile-incremental-synchronization-timer-job-stuck-at-88-status?forum=sharepointadminprevious
Or try to clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. Microsoft has provided a step by step procedure on clearing file system cache from the SharePoint front-end servers
in this kb article.
You can also see the ULS logs and check error messages.
http://sharepointlogviewer.codeplex.com/
Best Regards
Dennis Guo
TechNet Community Support

Backgroung jobs remain in "Ready" status

Similar Messages

Maybe you are looking for