When I go to "Workflow Reporting" my webtop is taking long time to respond, may be more than a minut

Hi,

When I go to "Workflow Reporting" my webtop is taking long time to respond, may be more than a minute. When I go to "Audit", it is still worse. It takes about two (2) minutes to get the results? I am not sure why it is happening, but I added lot of stuff to dm_process object under "Audit Management - Manage Auditing By Object Type" in DA. Is it causing this slowness or something else? If the reason for this slowness is what I added to dm_process object type, what exactly I need to add? What is the best practice in your experience?

Please share your knowledge and experience.

Thanks.

Find more posts tagged with

Documentum

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

BartThierens

We have encountered a similar issue.

Changing audit settings was not an option.

We were able to solve the issue by adding well placed indices on the audit table.

All comments

KSMatson

The slowness in generating workflow reports or viewing audit records is most likely due to large amount of data in the audittrail table. As the data in the audit trail grows, the DA interface will obviously take longer to render the page with the audit information.

From a design perspective audit management is driven by the business needs, but the workflow auditing can quickly fill up the audit tables, so to keep a check on them you can turn on the audit management job and set a cuttoff date accordingly, for how long you want to keep the audit records for. Instead of auditing all workflow events, you could narrow down to what really needs to be audited.

athati

Thanks Khurram.

Can you give me some typical fields to be selected for auditing? I know it depends on business requirements, but still I am looking for default or typical settings. If you can, please list them.

Thanks.

KSMatson

By default the dm_logon_failure and dm_default_set events are audited, you can read about them in the fundamentals guide.

The information for the types and events that are configured for auditing is recorded in the dmi_registry table, you can query it as follows

select * from dmi_registry where is_audittrail = 1;

Some other events worth auditing for dm_user would be dm_connect, dm_authenticate and for dm_sysobject dm_destroy event would be something worth having. For the different object types you can see what evenst are present to be audited by using the following query, below query shows available auditable events for dm_process object type

select auditable_sysevents from dmi_dd_type_info where type_name = 'dm_process' and auditable_sysevents is not nullstring enable(row_based);

BartThierens

We have encountered a similar issue.

Changing audit settings was not an option.

We were able to solve the issue by adding well placed indices on the audit table.

athati

Thanks Bart.

Can you please give me more details about adding well placed indices on the audit table...what is the audit table name in the database...what indices are added...how they are added etc.

Please post as many details as you can.

Thanks.