MarkView Performance Issues Related to Queries Against MV_SESSION_LOG

Issue

Our DBA has found that there is a MarkView performance issue related to queries against mv_session_log table in the MarkView schema.

Cause

• This can occur over time as old no-longer-required session data builds up in the mv_session_log table in the MarkView schema.
• Please review the Num_rows field for the MV_SESSION_LOG table in the Performance Information output of the MarkView Support Tools.
  • If there is over 500k rows, please take the following steps: 

Solution

1. Backup existing records (temporarily):

Create table mv_object_lock_bk as select * from mv_object_lock;

Create table mv_object_access_log_bk as select * from mv_object_access_log;

Create table mv_session_log_bk as select * from mv_session_log;

 

2. Delete the old records:

delete from mv_object_lock where markview_session_id in (select markview_session_id from mv_session_log where last_activity_timestamp < sysdate - 30);

delete from mv_object_access_log where markview_session_id in (select markview_session_id from mv_session_log where last_activity_timestamp < sysdate - 30);

delete from mv_session_log where last_activity_timestamp < sysdate - 30;

Commit;

 

3. Create the following index (if one does not already exist).:

Create index on MV_SESSION_LOG.LOGON_TIMESTAMP;

 

Level of Complexity 

High (Consult with your DBA before proceeding)

If you have any questions, please log a MarkView support case , ensuring you upload your current Performance Information output from the MarkView Support Tools when you do.

 

Applies to  

Product	Version	Build	Environment	Hardware
MarkView	All