Concurrent requests running long

Hi Erman,

We have upgraded EBS from 12.1.3 to 12.2.6
We are facing severe issue in concurrent requests.

If we run the code from toad it takes around 15-20 min.
for the same in concurrent program, it is taking hours to run.

Can you please help us with the same ?

Thanks,
Prafull

[ErmanArslansOracleBlog]

1)Did you check concurrent request traces?
2)Did you enable concurrent program db session trace and check?
3)Do you have sufficient concurrent processes defined for the relevant concurrent manager?
4)You may be spending time on other places rather than sql.. did you check the concurrent program and see what is designed to do? (I mean; maybe after querying the database, your conc programs do other things and you may be waiting for those other things..)

1)Did you check concurrent request traces?
No
2)Did you enable concurrent program db session trace and check?
No
3)Do you have sufficient concurrent processes defined for the relevant concurrent manager?
Yes, application is multinode and sufficient number of concurrent managers defined
4)You may be spending time on other places rather than sql.. did you check the concurrent program and see what is designed to do? (I mean; maybe after querying the database, your conc programs do other things and you may be waiting for those other things..)
How can I check whether exactly the concurrent program spending time ?


Thanks,
Prafull

[ErmanArslansOracleBlog]

Enable trace for the concurrent program.
Rerun it and check the trace...

Also, find the problematic concurrent program/programs name (using form screens). See if it is java, or plsql or script etc..
After that, check that program definition and see what it is written to do..

Hi ,

We able to fix this issue with help of our technical person.

As far as dba end was concerned, we were unable to get any recommendation though we did the analysis with the help of ADDM /AWR/ and SQLT.

Thanks,
Prafull

[ErmanArslansOracleBlog]

You needed to enable trace for the concurrent program, you needed to find the problematic SQL and you needed to check the knowledge base + consider sql tuning..
AWR could also tell you your problematics sqls and + db wide performance problems.
But, again since you already identified the problematic concurrent program, you needed check the sql trace of the concurrent request firstly..

Also, please share all the related info here. For ex: What did you do to resolve your problem?