Absent Member.. Absent Member..
Absent Member..
45 views

PPM Support Tip: Missing indexes on Database tables

KCS article: KM00681040

 
 
Is it safe to add indexes to PPM specific tables (for example FM_FORECAST_ACTUAL_LINES or FM_FINANCIAL_LINE_CELLS) to increase performance on views joining on these tables if these indexes are missing?

 

It is safe to add custom indexes on DB tables FM_FORECAST_ACTUAL_LINES and FM_FINANCIAL_LINE_CELLS; the issue is related to product defect QCCR1L45264, which reports missing indexes on several DB tables having foreign key constraints referring to non-indexed columns

 
The product defect QCCR1L45264 has reported that in PPM DB schema there are some tables with foreign key constraints, and no indexes defined on the referenced columns. The ticket is available on the SSO portal via the following URL:
http://support.openview.hp.com/selfsolve/document/LID/QCCR1L45264

Tables FM_FORECAST_ACTUAL_LINES and FM_FINANCIAL_LINE_CELLS are 2 of the tables from this defect.

 
QCCR1L45264 has been resolved in version 9.14.0006, and if you are running on a previous release, you can upgrade to 9.14.0006 or later release, which adds a new set of indexes on the foreign key columns.

Labels (1)
0 Likes
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.