Jobs are in ready state

Hi,
Kernel Release-701
OS-Linux
Patch level-117
dev_disp
ERROR => DpWPCheck: W55 (pid 7299) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=7299) killed with signal 11
ERROR => DpWPCheck: W56 (pid 7523) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=7523) killed with signal 11
ERROR => DpWPCheck: W57 (pid 23473) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=23473) killed with signal 11
ERROR => DpWPCheck: W58 (pid 7526) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=7526) killed with signal 11
ERROR => DpWPCheck: W60 (pid 7528) died (severity=0, status=11) [dpxxdisp.c   15884]
child (pid=7528) killed with signal 11
SM21 logs
08:00:05 BTC 055 000 SAPSYS                  EC F Failed to create log for job /
08:00:05 BTC 055 000 SAPSYS                  EA Y Failed to read status entry for job
08:00:05 BTC 055 000 SAPSYS                  EB C > Job
08:00:05 BTC 055 000 SAPSYS                  F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:00:05 BTC 057 000 SAPSYS                  EC F Failed to create log for job /
08:00:05 BTC 057 000 SAPSYS                  EA Y Failed to read status entry for job
08:00:05 BTC 057 000 SAPSYS                  EB C > Job
08:00:05 BTC 057 000 SAPSYS                  F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:00:06 BTC 060 000 SAPSYS                  EC F Failed to create log for job /
08:00:06 BTC 060 000 SAPSYS                  EA Y Failed to read status entry for job
08:00:06 BTC 060 000 SAPSYS                  EB C > Job
08:00:06 BTC 060 000 SAPSYS                  F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:00:06 BTC 056 000 SAPSYS                  EC F Failed to create log for job /
08:00:06 BTC 056 000 SAPSYS                  EA Y Failed to read status entry for job
08:00:06 BTC 056 000 SAPSYS                  EB C > Job
08:00:06 BTC 056 000 SAPSYS                  F2 0 Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')
08:00:06 BTC 058 000 SAPSYS                  EC F Failed to create log for job /
08:00:06 BTC 058 000 SAPSYS                  EA Y Failed to read status entry for job
Some jobs are going in ready state
If i check them then job execute successfully.

Hi,
As per my personnel experience, there are lot of errors in kernel support pack 117 of 701 release. Try to use patch level 111 which is good.
Also, run TEMSE consistency check to check any inconsistency.
Thanks
Sunny

Similar Messages

Scheduled jobs are in released state only

Dear Experts,
we shedule jobs in background periodically. But for a particular time, all scheduled jobs are in released state only. Please suggest what might be the issue. Even some SAP std jobs have have not started.

Hi Raghavendra,
Have you checked enough BTC work process available in your SAP system.
Use SM65 transaction,goto =>Additional Tests ;check mark "Determine work process status" and "Determine no of jobs in queue"
and see the test results for any problems.
Best Regards,
Shyam Dontamsetty

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

Messages are in READY state in QUEUE TABLE but in AQ$ QUEUE TABLE messages are in PROCESSED State

HI All,
   We create a brand new oracle multi-consumer queue. We have en-queued the messages into the queue and are processed successfully.
   But when we checked the STATE Column of the messages in the queue table it was showing as "0". But it is showing as "PROCESSED" in the
   AQ$<QUEUE_TABLE> msg_state column.
We are unable to figure out why there is a mismatch. Can any one help us ?
Regards,
Hari P.

Hello,
the column value AQ$<QUEUE_TABLE>.MSG_STATE = 'PROCESSED' corresponds to column value <QUEUE_TABLE>.STATE = 2
(see definition of view AQ$<QUEUE_TABLE for the DECODE statement).
In your case you see a value of STATE = 0 instead of STATE = 2. Is this correct ? The value 0 corresponds to a state "READY" (the delay
is gone and the message is ready for dequeuing).
The AQ documentation says: "After the specified delay, the message is in the READY state and available for dequeuing."
Normally, you cannot see the processed data in your AQ because the enqueued data will be deleted after
successful dequeuing. You wrote that they were processed successfully.
Kind regards,
WoG

Jobs are not in active state

Jobs are in Ready stage but it is not going to active what might me the problem. could any one can reply to my question.

Mani,
It looks like it is just created and in ready status without job start parameters, you can just hit the release icon (Green flag) in SM37 to run your job.
Regards,
Prasobh

Transaction/Report to process background work items which r in READY state

HI,
Can somebody kindly tell me the transaction/report program to process background work items which are in ready state. SM59 configuration was missing and hence, workflows failed to execute after being started successfully. Now, I want to comeplete these operations.
Thanks a lot,
Max

Hi Max,
Did you check transaction SWPC? If the workflows are in there you can start them through in a proper way.
Regards,
Martin

Messages in Ready state are not dequeuing.

Messages are being left in a "Ready" state. Everything was working fine in 10g. However there was an upgrade to 11g and now queues have stop working. It is a multiconsumer queue with one subscriber. I can manually dequeue messages but the subscriber call back does not seem to function.
-- Create and start queues and queue_table
BEGIN
     DBMS_AQADM.CREATE_QUEUE_TABLE (
          queue_table => 'muse.m_en_queue_table',
          queue_payload_type => 'muse.eu_logid_type',
          multiple_consumers => TRUE
     DBMS_AQADM.CREATE_QUEUE (
          queue_name => 'xxxxx.m_en_queue',
          queue_table => 'xxxxx.m_en_queue_table'
     DBMS_AQADM.START_QUEUE('xxxxx.m_en_queue');
     --Start Default Exception Queue
     DBMS_AQADM.START_QUEUE('xxxxx.AQ$_M_EN_QUEUE_TABLE_E', enqueue => FALSE, dequeue => TRUE);
     DBMS_AQADM.ALTER_QUEUE (
          queue_name => 'xxxxx.m_en_queue',
          max_retries => 2,
retry_delay => 10);
END;
--Procedure to dequeue messages and try to resend to the notification service
CREATE OR REPLACE PROCEDURE muse.m_en_queue_callback_procedure(
     context RAW,
reginfo SYS.AQ$_REG_INFO,
descr SYS.AQ$_DESCRIPTOR,
payload RAW,
payloadl NUMBER
) AS
     dequeue_options      dbms_aq.dequeue_options_t;
     message_properties      dbms_aq.message_properties_t;
     message_handle           RAW(16);
     o_payload      muse.eu_logid_type;
     change_rec           muse.eocd_update%rowtype;
BEGIN
dequeue_options.WAIT := DBMS_AQ.no_wait;
dequeue_options.msgid := descr.msg_id;
dequeue_options.consumer_name := descr.consumer_name;
DBMS_AQ.DEQUEUE(
queue_name => descr.queue_name,
dequeue_options => dequeue_options,
message_properties => message_properties,
payload => o_payload,
msgid => message_handle
END;
--Subscribed to queue
BEGIN
DBMS_AQADM.ADD_SUBSCRIBER (
queue_name => 'xxxxx.m_en_queue',
subscriber => SYS.AQ$_AGENT(
'muse_en_queue_subscriber',
NULL,
NULL )
DBMS_AQ.REGISTER (
SYS.AQ$_REG_INFO_LIST(
SYS.AQ$_REG_INFO(
'xxxxx.M_EN_QUEUE:MUSE_EN_QUEUE_SUBSCRIBER',
DBMS_AQ.NAMESPACE_AQ,
'plsql://xxxxx.m_en_queue_callback_procedure',
HEXTORAW('FF')
1
END;
/

Hi,
What version specifically of 11g did you upgrade to?
Did you review the following MOS notes?
Event Monitor Process: Architecture and Known Issues (Doc ID 105067.1)
AQ PL/SQL Notification No Longer Work Due To "register_driver()" Jobs Not Terminating (Doc ID 331372.1)
Thanks
Paul

Jobs are going to released state after the PC triggers with user event.

HI BI experts,
We are facing issue with event scheduler using user event in the process chains. Some Jobs are not starting immediately with the event and reaching release state. These released jobs are never starts in near future. Also cannot start manually due to event periodic jobs.
No log is availble in SM61 due to settings.
Please let me know your suggestions and this issue.
Regards,
Mohan.

HI BI experts,
We are facing issue with event scheduler using user event in the process chains. Some Jobs are not starting immediately with the event and reaching release state. These released jobs are never starts in near future. Also cannot start manually due to event periodic jobs.
No log is availble in SM61 due to settings.
Please let me know your suggestions and this issue.
Regards,
Mohan.

Why are messages not dequeuing and stuck in the ready state?

Messages are successfully enqueueing but not dequeuing and are stuck in ready state (STATE = 0). The ENQ_TIME is 5 hours ahead of system time. In one environment, AQ is working (10g 10.2.0.4.0). In the other environment, it is not working (11g 11.2.0.3.0).
I just did the following:
1. Purged queue table
2. Stopped queues
3. Dropped queues
4. Dropped queue table
5. Created queue table
6. Created queues
7. Started queues
I tested once and a record was inserted in the queue table:
MSGID      <msgid>
CORRID
PRIORITY      1
STATE      0
DELAY
EXPIRATION
TIME_MANAGER_INFO
LOCAL_ORDER_NO      0
CHAIN_NO      0
CSCN      0
DSCN      0
ENQ_TIME      12/23/2014 4:33:43.338902 PM
ENQ_UID      <enq_uid>
ENQ_TID      <enq_tid>
DEQ_TIME
DEQ_UID
DEQ_TID
RETRY_COUNT      0
EXCEPTION_QSCHEMA
EXCEPTION_QUEUE
STEP_NO      0
RECIPIENT_KEY      0
DEQUEUE_MSGID
SENDER_NAME
SENDER_ADDRESS
SENDER_PROTOCOL
USER_DATA      <user_data>
USER_PROP
Notice the RETRY_COUNT is 0. The ENQ_TIME is 5 hours ahead. In the procedures to enqueue and dequeue, there are no errors.
Following is the plsql to enqueue:
CREATE OR REPLACE PACKAGE BODY
pkg_2
AS
    FUNCTION queue_create_thing ( <parameters> )
        RETURN NUMBER
    IS
        enqueue_options     dbms_aq.enqueue_options_t;
        message_properties dbms_aq.message_properties_t;
        message_handle      RAW(16);
        v_message           msg_type;
        v_thing_id          things.id%TYPE;
    BEGIN
        v_message := msg_type( <parameters> );
        dbms_aq.enqueue(queue_name => '<queue name>',
                        enqueue_options => enqueue_options,
                        message_properties => message_properties,
                        payload => v_message,
                        msgid => message_handle);
        RETURN v_thing_id;
    EXCEPTION
        WHEN OTHERS
        THEN
           errpkg.record_and_stop (SQLCODE);
    END queue_create_thing;
    PROCEDURE queue_delete_thing( <parameters> )
    IS
        enqueue_options     dbms_aq.enqueue_options_t;
        message_properties dbms_aq.message_properties_t;
        message_handle      RAW(16);
        v_message           msg_type;
    BEGIN
        v_message := msg_type( <parameters> );
        dbms_aq.enqueue(queue_name => '<queue name>',
                        enqueue_options => enqueue_options,
                        message_properties => message_properties,
                        payload => v_message,
                        msgid => message_handle);
    END;
END pkg_2;
Following is the code to dequeue:
CREATE OR REPLACE PACKAGE BODY
pkg_1
AS
    PROCEDURE create_thing ( context IN RAW,
                                reginfo IN sys.aq$_reg_info,
                                descr IN sys.aq$_descriptor,
                                payload IN RAW,
                                payloadl IN NUMBER )
    IS
        dequeue_options dbms_aq.dequeue_options_t;
        message_properties dbms_aq.message_properties_t;
        message_handle RAW(16);
        message msg_type;
    BEGIN
        dequeue_options.msgid := descr.msg_id;
        dequeue_options.consumer_name := descr.consumer_name;
        DBMS_AQ.DEQUEUE(queue_name => descr.queue_name,
                        dequeue_options => dequeue_options,
                        message_properties => message_properties,
                        payload => message,
                        msgid => message_handle);
        pkg_2.create_thing( p_thing_id => message.thing_id );
        UPDATE table t
           SET creation_complete = 1
         WHERE id = message.thing_id;
        COMMIT;
    EXCEPTION
        WHEN OTHERS
        THEN
            ROLLBACK;
            plog.error(SQLERRM);
            plog.full_call_stack;
    END create_thing;
    PROCEDURE delete_thing ( context IN RAW,
                                reginfo IN sys.aq$_reg_info,
                                descr IN sys.aq$_descriptor,
                                payload IN RAW,
                                payloadl IN NUMBER )
    IS
        dequeue_options dbms_aq.dequeue_options_t;
        message_properties dbms_aq.message_properties_t;
        message_handle RAW(16);
        message msg_type;
    BEGIN
        dequeue_options.msgid := descr.msg_id;
        dequeue_options.consumer_name := descr.consumer_name;
        DBMS_AQ.DEQUEUE(queue_name => descr.queue_name,
                        dequeue_options => dequeue_options,
                        message_properties => message_properties,
                        payload => message,
                        msgid => message_handle);
        pkg_2.delete_thing( p_thing_id => message.thing_id );
        COMMIT;
    EXCEPTION
        WHEN OTHERS
        THEN
            ROLLBACK;
            plog.error(SQLERRM);
            plog.full_call_stack;
    END delete_thing;
END pkg_1;

Following is the code to create the queue:
BEGIN
SYS.DBMS_AQADM.STOP_QUEUE ( QUEUE_NAME => '<queue name>');
SYS.DBMS_AQADM.DROP_QUEUE ( QUEUE_NAME => '<queue name>');
END;
BEGIN
SYS.DBMS_AQADM.CREATE_QUEUE
    QUEUE_NAME          =>   '<queue name>'
   ,QUEUE_TABLE         =>   '<queue table>'
   ,QUEUE_TYPE          =>   SYS.DBMS_AQADM.NORMAL_QUEUE
   ,MAX_RETRIES         =>   5
   ,RETRY_DELAY         =>   0
   ,RETENTION_TIME      =>   0
   ,COMMENT             =>   'Queue for processing creation of things'
END;
BEGIN
SYS.DBMS_AQADM.START_QUEUE
    QUEUE_NAME => '<queue name>'
   ,ENQUEUE => TRUE
   ,DEQUEUE => TRUE
END;

RAR jobs in ready state

Hi,
When I schedule batch jobs for user/role full sync. Its going into ready state, kidnly suggest

Hi Yash,
check if your background job deamon runs.
Material to read is here: SAP GRC Access Control 5.3 - Post-Installation - RAR
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60706c35-1f57-2b10-e0bf-82dc433e94f4
Regards,
Frank

Spawn jobs are not getting priority and target servergiven at selection scn

Hi Abapers,
I am scheduling main program as a job in backend through FMs JOB_OPEN, JOB_SUBMIT and JOB_CLOSE with priority and target server taken from user at selection screen through SE38,after executing the job,job will generate the spawn jobs (i.e child jobs). The spawn jobs also be scheduled with same priority and target server from taken user. But after completion of main job execution, the spawn jobs are not generating with same priority and target server taken from selection screen. May be its getting refreshed.
Please give me an idea how the spawn jobs also have to get the same priority and server of main job?
Please reply as soon as possible. I need it urgently.

Hi,
I have used below statements for ADD EXTRACT and ADD REPLICAT.
------Extract
ADD EXTRACT ext_1, TRANLOG, BEGIN NOW
-------Data Pump
ADD EXTRACT pump_1, EXTTRAILSOURCE /app/ggs/trail/local_trail_1/ta, BEGIN NOW
-------Replicat
ADD REPLICAT rep_1, EXTTRAIL /app/ggs/trail/remote_trail_1/tb, BEGIN NOW, CHECKPOINTTABLE ogg.tarun_chk
Yes, i have tried tutorial at Oracle Learning Library.
Thanks
Tarun
Edited by: user8886876 on Feb 12, 2012 9:56 PM

Job is in scheduled state for longer time.

Hi All,
I am running a load which involves extraction from source system. The load was taking longer than the usual time. I grew suspicious and checked the status of the job in the source system. But that was sitting in the scheduled state and when i try to change the job status , not able to do so. I checked the BGD processes availability and they were all in waiting status.
What can be done for this? Suggest ....

Hi..the issue you have is probably due to the fact that already a lot many jobs are running in background in your R/3 system and unless they finish you job will not get any background processes to get it to active state from the scheduled state.
Now thats why usually BW loading are done at night or off hours of business when transactions or r/3 jobs are not running much.
Schedule your job at a time when background processes are available then you won't face this issue.
Contact the basis handling the R/3 system.
Regards,
RK

UCCE 7.5(8) CAD 7.5.1.59 got blocked in Working Ready state

Hi all,
We're using UCCE 7.5(8) with CAD 7.5.1.59. From time to time, we remarked some CAD get blocked in the Working Ready state after ending a call.
Our wrap up time is currently configured to 2 hours (as requested by client) so the CAD wont turn back to Ready state automatically.
The CAD can be unblocked by an internal call (no UCCE)
Anyone experiences the same problem?
Thanks in advance.
Best regards,

@Geoff:
Thank you for all the good sugesstions, however unfortunately none of them is possible to me
I would try this using the CTIOS client on your test machine, just to eliminate CAD a little. From the trace, it doesn't appear to matter, since you are looking at the pure CTIOS trace messages, and they are the issue - but I like CTIOS for this sort of debugging.
--> We are using CAD and do not have CTIOS client installed. Does the soft actually come with the UCCE installation package? Can you please tell me where I can find it?
@Geoff and Ed
Dissociate and re-associate the device with JTAPI and retest.
--> Good point, I did the same actually but the phone still didn't work.
Nevertheless, I really think we have a network problem (which was observed time to time before)
I will update this thread as soon as I can do some further tests.
Thanks,
Regards,

Cancel and keep workitem in ready state in user decision step

Hi,
In a user decision step,there is a default option 'Cancel and keep the work item'.
Now clicking on this option, the workitem goes into "Inprogress state"
whereas i want to keep the workitem in "ready state" after i click on the option 'Cancel and keep the work item'.
I am trying to modify the Process method of Decision Object type to incorporate this funcationality by using FM "SAP_WAPI_PUT_BACK_WORKITEM.
but im getting the error that this FM cannot be used at runtime.
Place where im trying to call this FM:
After the FM'SWU_PROCESS_MANUEL_DECISION'
I am getting the value of RESULT.
If result is SPACE or sy-subrc is not 00 then i am calling this Fm which takes Wi_id of the userdecision as input.
Kindly help
Regards

Hi,
Let me ask you this. Why you need to have this in "Ready" state, Not in "IN PROCESS" state. Anyway, the witem is still there in the user's inbox, and if you have any deadline monitoring, then this is also taken care with "Cancel and keep xxxx". So, i think, functionally you'll still be better with the existing functionality.
And, with all this, if you are still trying to change, then i think it's NOT possible. If i understand correctly, you are trying to use the FM "SAP_WAPI_PUT_BACK_WORKITEM" within the PROCESS method. And, if you understood the functionality of how this works, you are trying to set the status of the SAME witem for which you are executing the PROCESS method.
THe way i understand the behind-the-scenes process, once you make a decision and save, this method is the one which in turn sets the witem status. And within that, you CANNOT capture the status as it is yet to be posted to the Witem tables.
Probably, after this decision step, use a different background task with the above FM to set the witem status to "Ready", BUT NOT IN THE SAME METHOD of PROCESS.
Also, it's not advisable to change this std. method.
Hope this helps you. Reply,if you need more info.
venu

Send Mail step in ready state

Hello Experts,
I am a workflow novice, just starting out.
I have copied the standard PO release workflow - WS20000075 and inserted a send mail step before activity "Release of purchase order". This was because I would like to send the PO as a PDF attachment to the approver.
The send mail step works fine (i have custom object and method to attach and send mail), it sends out the mail with the attachment correctly, but the work item is in "ready state" and needs to be manually "completed" for the workflow to proceed. After this, the workflow proceeds perfectly.
The send mail is marked as a background task and synchronous object method.
What do i need to do for the "Release of purchase order" to happen as soon as the email has been sent out?
Thanks a lot for the help.
Regards,
Parag.

Hello Ravi,
Thanks for the prompt reply, there are no erros in the workflow log.
SWU3 was definitely done, standard PO Release workflow works fine and so do other ones. Its just that I copied the standard and inserted a new step.
Do I somehow need to "terminate" the send mail step for the workflow to move over to the next activity ?
Regards,
Parag.

Jobs are in ready state

Similar Messages

Maybe you are looking for