06-20-2014 12:08 PM
Hi Gurus,
There is situation in our PRD environment /POSDW/OUTBOUNDDISPATCHER Job running for 4500 to 6000 seconds, even after Idocs (WPUUMS & WPUTAB) are created in ECC.
Is there any workaround that need to be done? any approach highly appreciated!
Thanks and Regards,
Ramesh D
06-20-2014 12:32 PM
Hi,
Can you check what tables it is reading in background ?
SM50
Thanks,
Vikrant.
06-20-2014 12:45 PM
Hi Ramesh,
Generally it happens because of huge data in POSDM workbench...You can check records count & how many days data you have in POSDM workbench and If counts are huge I suggest you can perform housekeeping for the same based on confirmation with your business...
Normally housekeeping of transactional data is recomendded to avoid performance... We have standard transaction /N/POSDW/DELE to delete old pipe data from workbench...
BR
Ajaya Kumar Mishra
06-20-2014 12:49 PM
I have performed traces of job ISAPXPO020 and compared the results
with the trace performed. On both traces most of
the time is spent on update operations on table /PODW/AGGR.
Looking at the trace details we can see that on both traces the
optimizer is using the same access path. However average time per
execution on today's trace is much better than on Monday (0.5ms vs
3.6ms). This would indicate that response times increases were due to
I/O issues. Therefore we would recommend that you investigate IO
performance over the last few days (e.g. operating system, file
system, connection to I/O sub system, I/O sub system itself) that
would explain increase in update times.
We would also recommend that you implement recommendation from my
colleague Rita Flohr regading the very high number of updates on table
/PODW/AGGR.
06-20-2014 12:53 PM
Hi Ajay,
Its processing only 100 records, reason is what, i'm raising this query?!
Thanks and Regards,
Ramesh D
06-25-2014 4:53 PM
06-25-2014 6:21 PM
07-31-2014 6:42 AM