Oracle stored procedure job running long time from DS

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
pimmit22043
Participant
Posts: 38
Joined: Thu Jul 26, 2007 6:11 am

Oracle stored procedure job running long time from DS

Post by pimmit22043 »

Hi

We have a job that calls the oracle stored procedure(using stored procedure stage), which is running long time from DS parallel job about 20 hours and we have ran the stored procedure from SQLPLUS, it ran about 2 to 3 hours and we also ran the SP from DataStage server using SQLPLUS, it completed with in 3 hour,

Did anybody came across this kind of problem running long time or can anybody has any ideas, please share.
-RK
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post by asorrell »

Not really - the first thing I would do is have your Oracle DBA check to see what threads are being started in Oracle and what differences, if any, he can see between the two separate executions.
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
pimmit22043
Participant
Posts: 38
Joined: Thu Jul 26, 2007 6:11 am

Post by pimmit22043 »

Thanks for your time,

basically he is saying both separate executions are same and explain plans are same.
-RK
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post by asorrell »

At that point I'd contact your Service Provider to see what they say. I've not seen this behaviour (and we do a LOT of Stored Procedures with Oracle) and if the explain plans are the same it sounds like there may be some sort of resource constraint being applied by PX that isn't readily viewable.
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
John Smith
Charter Member
Charter Member
Posts: 193
Joined: Tue Sep 05, 2006 8:01 pm
Location: Australia

Post by John Smith »

How does your job look like? When you run it using the Stored Procedure stage, all it does is pass the parameters back to the database so in essence it should be the same. I done it before and performance is the same. Has this problem just happened recently? has your job been able to run well in the past?
DS consultant.
pimmit22043
Participant
Posts: 38
Joined: Thu Jul 26, 2007 6:11 am

Post by pimmit22043 »

We have added the NLS_LANG parameter to the project as none value and called this parameter to the job,now stored procedure run with in couple hours.
-RK
Post Reply