Why "dm_getfile" can only get records start from March???

Hi , I'm new to Documentum and DQL.

I want to get records of what files were viewed/exported by users. I'm using DQL select * from dm_audittrail where event_name = 'dm_getfile'. it will supose to collect all records in content server, correct? But what I can get is only records from March of this year. why?

Is there any time limit for audit trail?

Documentum version 5.3.

Hope some expert can help on this...thanks!

Find more posts tagged with

Comments

AlanZ

Moved to the Documentum community

Jeremy Saumen

Hi,

Check if you have configured the dm_job "dm_AuditMgt", especially the "cutoff_days" and "custom_predicate" arguments.

The job destroys all dm_audittrail older than the cutoff_days argument and that matches the custom_predicate argument.

Jeremy Saumen

By the way, when the job is invoked, one or several dm_audittrail are created, you can check this with this query :

select * from dm_audittrail where event_name = 'dm_purgeaudit';

mj312

Hi Jeremy, thanks for your reply. Yes there is a dm_job "dm_AuditMgt” with arguments "cutoff_days 90" and "custom_predicate r_gen_source=1" What does the argument "custom_predicate r_gen_source=1" means? And if I changed the cutoff_days from 90 to 180, what’s the impact? Will it heavy server’s workload?

Jeremy Saumen

Hi,

custom_predicate is used to delete only dm_audittrail which verifies the condition (in your case, only the dm_audittrail with r_gen_source=1 are deleted)

cutoff_days with 180 will delete dm_audittrail with a time_stamp older than 180 days (and which verifies the custom_predicate parameter). There can be a performance issue : the tables behind dm_audittrail will be bigger and inserting data can be slower. For the delete process, if you don't change the schedule, the workload should be more or less the same.

You should check the Content Server Administration Guide, "Audit Management" section for more informations and the full list of options.

Here, we didn't want to lose the dm_audittrails but we didn't want to have a performance issue so we implemented a custom method to archive the dm_audittails in an archive database.