Re: Spinning package call

Posted by Laurel on Jun 21, 2018; 1:11pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Spinning-package-call-tp6218p6229.html

Hi Erman!
Thx  for ideas..
1. We dont have this as top5 and also not other sessions waiting on it
2. If it would be resource mgr I would see it on the OEM/top wait events
3 Not othersessions and not in top 5 awr
4. Not using parallel
Event Waits Total Wait Time (sec) Wait Avg(ms) % DB time Wait Class
DB CPU                  3146,6                44.4
db file sequential read 2,242,204 757,5 0.34 10.7 User I/O
log file sync 36,844 159,9 4.34 2.3 Commit
db file parallel read 114,092 112,9 0.99 1.6 User I/O
direct path read 67,739 112,8 1.67 1.6 User I/O

Its on CPU constanly.Taking 1 CPU.
As this is plsql call and I cannot see anything  in trace .. Only that its spinning.
 I asked developer to include plsql hierarchial  profiler calls to package and debug it
The problem is that trace became from profiler 30Gb and we cannot analyze it / session crashes on out of memory when using plsql profiler,analyze call

Now I asked developer to cut in chunks package  and make more multilple traces files..

Do you have any other idea how to analyze in that case  from db perspective ?
Some loop in loop and in loop call i affraid..

Appreciate any ideas!
Thx laurel