URGENT - posted in techie forum aswell.

We upgraded our live environment to STND/TOOLS weekly dumps 26/05, porting set 7.1d.09 and associated bic and bshell files.

All looks well except simulate orders cprrp1210m000 performance has been impacted. This has gone from running for 1 hour to taking upto eight hours to complete since the upgrade :( . This is the same for all our logistic companies.

No error messages in logs, it just is taking a long time to run.


Anyone got any ideas as to why, or had a similar problem after upgrade. Logged a case with SSA but thought someone on here may have some input.

Thanks for the help.

Dave

URGENT

We upgraded our live environment to STND/TOOLS weekly dumps 26/05, porting set 7.1d.09 and associated bic and bshell files.

All looks well except simulate orders cprrp1210m000 performance has been impacted. This has gone from running for 1 hour to taking upto eight hours to complete. This is the same for all our logistic companies.

No error messages in logs, it just is taking a long time to run.


Anyone got any ideas as to why, or had a similar problem after upgrade. Logged a case with SSA but thought someone on here may have some input.

Thanks for the help.

Dave

Dave, for your information: one thing you should certainly not do on this forum, is crossposting messages (posting same message at different sections); the members and the boardmasters do not appreciate this....

Hi Apologies for this, I was just trying to get the view of the EP GURUS and the techie Gurus.

Dave

I didn't suspect you doing this on puspose, I just wanted to give you this tip...

Start the job/session with this option, probably will give you some hints about what SQL statement is taking that long.

Threads have been merged :)

Thanks Han. I have done this but it doesnt seem to shed amy light on log sql statements. the longes one was 0.63 of a second. I have sent a profile to SSA to see if they uncover anything.

Any further advice.

Thanks

Dave

Try to keep the same old object and check the performance..
if it works then Im my view you have to optimize the object using sqltrace..

Amolpk

Hi All, Thanks.

It looked like a solution in the weekly dumps was causing this issue. This has been removed and the jobs now run fine. Have taken this up with SSA to find out way forward regarding solution.


thanks for the help

Dave