Skip to main content
Kofax

Markview Performance - Additional Foreign Key indexes - 6.4 and 6.5 versions

Summary

11918

Applies To

  • ERP System: Oracle
  • MarkView Version: 6.4 and 6.5

Behavior

Performance issues may be encountered in MarkView as a result of blocking SQL sessions. This is generally seen in environments where the database is upgraded or patches applied which causes differences of how the optimizer handles database locking.

Resolution

Customers running MarkView 6.5 and 6.4 for Oracle should apply the following Hotfixes which add additional foreign key indexes:

  1. MarkView 6.5 - FIX1131 - Resolves database contention due to unindexed foreign keys
  2. MarkView 6.5 - FIX1133 - Resolves Row Contention on MV_PAGE_MARKUPS_VIEW
  3. MarkView - FIX1240 - Resolves a database contention issue due to unindexed foreign keys
  4. MarkView 6.5 - FIX1046 - Resolves an issue where locks on MV_DOCUMENT are caused by missing indexes
  5. Additional Foreign key indexes are required on the following tables:
    1. CREATE INDEX MV_DOC_CREATION_USER_ID_FK ON MV_DOCUMENT (CREATION_USER_ID) TABLESPACE &MV_TABLESPACE;
    2. CREATE INDEX MV_PAGE_MARKUP_PAGE_ID_FK ON MV_PAGE_MARKUPS_VIEW (PAGE_ID) TABLESPACE &MV_TABLESPACE;

Customers running MarkView 6.5 should also apply this fix:

MarkView 6.5 - FIX1132 - Resolves Row Contention on MV_OBJECT_AUTHORIZATION

Customers running Markview 6.4 should also apply this index:

CREATE INDEX MV_ATH_USER_ID_TS_NDX ON MV_OBJECT_AUTHORIZATION (USER_ID, ENABLE_TIMESTAMP) TABLESPACE &MV_TABLESPACE;

After applying these fixes ensure that statistics are gathered and rebuild the indexes per the following article:

How do I rebuild the indexes on the sf_event_alert and sf_event_alert_property_value tables?

Keywords: foriegn