dm_clean tool failed issue

Pradeepgaddipati

Hi Experts,

i am facing problem with dm_DMClean job.. after the job ran , In last run status i am getting below error

DMClean Tool Failed-- check that sysadmin dir exists and has sufficiently open permissions

Please do the needful to resolve the issue.

Thanks in advance

Regards,

Pradeep

Find more posts tagged with

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

rstein

Hello.

You may have deleted the log directory containing the session logs, there must exist a subdirectory "sysadmin", if it doesn't then the job reports can't be generated. This directory is not created automatically if you delete them any time after the docbase is created, its path is \Documentum\dba\log\<hex repository id>\sysadmin.

Manually creating this directory and granting full control permissions to the Installation Owner should fix the problem.

Regards.

All comments

rstein

Hello.

Manually creating this directory and granting full control permissions to the Installation Owner should fix the problem.

Regards.

Pradeepgaddipati

Hi,

Thanks a lot... sysadmin folder missed under the directory after creating the folder dm_clean job is working ..

Thanks you so much..

Regards,

pradeep

Pradeepgaddipati

I have one more question..

can you please tell me the exact diff b/w dm_DMclean and dm_DMfilescan

Thanks,

Pradeep

rstein

Dmclean will remove orphaned dmr_content objects along with their content files, in other words, dmr_content object which don't have related dm_sysojbect objects anymore. It does also some other cleaning that is described in the administrator guide. This job should be scheduled for a regular execution.

DMfilescan is used to locate and removed orphaned content files, that is, files that don't have their respective dmr_content objects anymore. This could be caused after a content file recovery is made from a backup in a point in time after (more recent) than the metadata. The tool scans every content file and searchs for its corresponding dmr_content object, if found to be orphaned, it is deleted. This tool don't need to be run regularly.