Clearing Documentum Object Cache

There may be a time when you need to force the Documentum object cache to be cleared on various servers. Consider these guidelines below when you receive an error such as the following:

DM_API_E_EXISTS error:Document/object specified by <ID> does not exist

Consider the following API statements on the server that is accessing the session:

API>kill,c,<objectID>

API>flush,c,ddcache,<object_type of the objectID in question>

API>flush,c,querycache

API>flush,c,persistentcache

API>flush,c,persistentobjcache

API>flushcache,c

On Documentum 6.5 and above, cache exists on the Content Server and the Application Server/s. On the Content Server, the cache exists in the following directory:

• • $DOCUMENTUM_SHARED/cache

If you are able to bounce the services then you can complete the following guidelines:

The process for clearing the cache on the Content Server is as follows:

• 1. Login as the installation owner

  2. Stop the Content Server processes for JMS, Docbase, and Docbroker (in that order)

  3. cd $DOCUMENTUM_SHARED/cache

  4. rm –R 6.5.0.xxxxxx

  5. Restart docbroker, docbase/s, JMS (in that order)

On the Application Server, the cache for EACH application is stored in the following directory:

• • .../documentum/cache

The process for clearing the cache on the Application Server is as follows:

1. Shutdown the Server

   1. cd documentum/cache

   2. rm –R 6.5.0.xxxxxx

2. Restart the Server