Indexes can become skewed if you frequently access parts of the index and not others. As a result, disk contention may occur and create a bottleneck in SQL performance. To prevent this performance degradation, you should monitor your P6 EPPM indexes and rebuild if necessary.
You can use the analyze_P6EPPM_indexes.sql
script to compute statistics on the P6 EPPM index, validate the index structure, and return a report that includes the following information:
The indexes that are returned from this report should be considered for a rebuild as they could represent a skewed tree structure and can lead to unnecessary database block reads of the index.
To run analyze_P6EPPM_indexes.sql
:
analyze_P6EPPM_indexes.sql
from https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=1327603.1&attachid=1327603.1:ANALYZE_INDEXES&clickstream=yes.
sqlplus <admuser>/password@<db_tns_names_entry>
@analyze_P6EPPM_indexes.sql
If you need to rebuild an index, you can run the following script:
ALTER INDEX <Index_Name> REBUILD ONLINE;
Where: <Index_Name> is the name of the index returned in the report.
Partitioning Oracle Database Tables for P6 EPPM Schema
Gathering Statistics for Cost Based Optimizations
Viewing the USESSION Table for GET_SAFETY_DATE
Where to Find Additional Oracle Database Tuning Information
Legal Notices
Copyright © 1999, 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Friday, September 30, 2016