Concurrent Managers Health Tip #1 – Rebuild your indexes!
This is really a simple one and you would be surprised how manycompanies large and small overlook this.
I have seen examples of sites with over 50 million rows inthe fnd_concurrent_requests_u1 indexes; a hugewaste of space! More importantly however is the problem of poor performance insuch a core OEBS activity e.g. 10 concurrent manager processes running with a30 second sleep time equates to 28,800 hits on your fnd_concurrent_requeststable and its indexes (this does not include your users submitting requests andchecking if their requests have completed). Get the picture why this is soimportant.
As part of regular maintenance practices you should rebuildyour indexes on routinely purged objects on a regular basis, especially theindexes on fnd_concurrent_requests.
Want to know if you need to rebuild your indexes? Thefollowing article includes everything you need to know together with code andthere is also a TOAD report. These can be found on the PIPER-Rx “tips” page: http://www.piper-rx.com/pages/tips.html
Rebuilding indexesin an OEBS environment - A guide to rebuilding indexes in an OEBSenvironment
View and Download associated TOAD report (TRD format) - Report id - FDBA002-10
Also remember some OEBS application monitors provide alertingto remind you when your indexes may need maintenance.
Happy Rebuilding J
