Skip to Content
avatar image
Former Member

Job RDDIMPDP Delayed

Hello !!!!

I have a little ploblem in my ECC 6.0 ehp 4 systems in hp-ux

my system consist of "2 dbs, 2 ascss, 5aps"

ploblem is rddimpdp Delayed about 40~60 seconds

when I saw the job logs in SM37, rddimpdp running in random servers every time

so, I shutting down 4ap servers, and retry cts & using tp command

It works normally, (it means no delayed rddimpdp)

but, when I start 2 servers, rddimpdp delayed.

I checked permission of filesystem, timezone, scheduled in client 000

can you tell me, what is the reason?

what can i do for fixing job delayed?

please help me !!

sleep does not come out of curiosity !!

yours truly.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Mar 04, 2014 at 02:20 AM


    can you tell me, what is the reason?

    RDDIMPDP is actually starts all the transport steps comes from tp via different separate batch work processes.  it all depends on the parameter rdisp/wp_no_btc, default you should have atleast 2 batch processes to start. if you have more work processes then obvious RDDIMPDP finish very fast.

    If your system has more application instances, we can distribute to different work processes from all the application servers via message server. check the note

    I could say, this is the reason, when you run on 4app servers, the job quite fast than the 2 app servers.

    other work arround i could suggest to check the batch work process count or set the operation modes to get more batch work processes.

    or check out other suggestions here  386646 - Event-controlled jobs start with a delay



    Add comment
    10|10000 characters needed characters exceeded

  • Mar 04, 2014 at 12:46 AM


    Is rddimpdp the only job that is delayed on your system ?

    If it is the only job that delayed then it can be a sapevt related issue.


    1158425 - Load balancing for events triggered by sapevt

    new procedure that uses round robin to distribute events triggered by sapevt to the relevant application servers.

    To activate the new procedure, use the following profile parameter (by default, the system uses the old procedure):
    ms/sapevt_lb = 1

    1147300 - Functions of the transport profile parameter BATCHHOST

    Add comment
    10|10000 characters needed characters exceeded