Documentum Housekeeping Jobs

I wrote a paper a few years ago on the importance of configuring and running seven Documentum housekeeping jobs (you can find the paper here and on the EDN).  It still amazes me how many times I come to client sites and find that these jobs are inactive and have never (or rarely) been run.  One of the first things I do when I come to a client site is check the reports from these jobs.  These reports give good insight to the state, condition and configuration of a Docbase.  However, if these jobs have not been run (or run recently) the environment is not taking advantage of the utility they offer.  And clients wonder why the system seems sluggish or is eating through disk space at a ravenous rate?

In my paper, Seven Jobs Every Documentum Developer Should Know and Use, I provided a schedule for seven important housekeeping jobs, but the context was for a development environment, not a production environment.  So, what should the schedule of jobs look like for a production environment?  I suggest the following:

Job Schedule
 dm_DMClean At least once every month.
(Ensure the clean_now argument is TRUE or the job will not execute the clean script.  Running this job will make it impossible to undelete objects.)
 dm_DMFilescan At least once every two months.
(Ensure the scan_now argument is TRUE, otherwise the files are not deleted).
 dm_LogPurge At least once every week.
(Change the cutoff_day argument to 90 or 120 days.)
 dm_ConsistencyChecker At least once every week.
 dm_UpdateStats At least once every week.
(Change the dbreindex argument to FIX or this job will only report DB statistics instead of update them.)
 dm_QueueMgt At least once every week.
 dm_StateOfDocbase At least once every week.

Caveat: Everyone’s operating environment and requirements are different.  Some of the frequencies recommended here may not be appropriate for your situation.  If so, make the changes appropriate for your environment or operating requirements.  Whatever you do, run these jobs; if not on this schedule, at least on a schedule.  Your Docbase will be happier.

If you are curious about how jobs are run in Documentum, see Robin East’s excellent write up here http://www.xense.co.uk/resources_docjs.htm.

Advertisements

About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

2 Responses to Documentum Housekeeping Jobs

  1. Matt says:

    Hi Scott. Good article, but a couple of clarifications that may help people…

    dm_DMClean job – the clean_now arguement defaults to true. Page 484 in 6.5 admin guide.

    dm_DMFilescan – the scan_now arguement defaults to true. Page 489 in 6.5 admin guide.

    dm_Logpurge – I created two instances of these, one for each content server in HA. Also, I set the cutoff to 92 instead of 90 so that I can clip the audit trail of the job log file using a query on the dm_AuditMgt job for any job log files older than 90 days.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: