View Single Post
  #7 (permalink)  
Old November 28th, 2007, 16:28
miks miks is offline
Junior Member
 
Join Date: May 2007
Posts: 19
Thanks: 1
Thanked 2 Times in 2 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 0
miks is on a distinguished road
Re: Purging and Archiving

Four months is about the time it takes for the order release refnum table to become the performance culprit. More than likely, if you take your saved queries and analyze them separately, you'll probably see full table scans. If you have already taken the normal steps of pinning all the big packages
(i.e. run: sys.dbms_shared_pool.keep'GLOGOWNER.VPD');
And, have a job that rebuilds all the otm indexes on an occasional basis.
And run analyze on a weekly basis.

Then try altering your saved queries. A good "trick" is, when quering reference data, instead of using "Begins With" "A", try using "Contains" and then providing more info to the code, like "ABC CORP". You'll notice a huge performance gain in the saved query, which, in turn will improve the business monitor. In general, if the business monitor takes more than 5 seconds to bring up, you definitely have a poorly performing query within it.

As you have also found out, tuning should be done within a domain user, not DBA.ADMIN.

Hope this helps.

Mike
Reply With Quote