Infrastructure at your Service

Stephane Biehler

Documentum xPlore: Several ways to start an Index Agent

In order to start index agents, you have several ways, depending on how you need to start them.

1. Use the documentum job dm_FTIndexAgentBoot. If you setup start_index_agents=T in the server.ini, the job will be called when the docbases are started.

2. Use the web interface:
Login to http://server:9200/IndexAgent/ with docbase credentials and select “Start in normal mode”

3. Login to DA and go to Indexing Management -> Index Agents and Index Servers
Right click on an index agent and select “Start Agent”

4. Use IAPI command to start it:

select index_name from dm_fulltext_index;
select object_name from dm_ftindex_agent_config;


5. Use Java:
java -cp $DM_HOME/lib/server-impl.jar:$DOCUMENTUM/dfc/dfc.jar com.documentum.server.impl.utils.IndexAgentCtrl -docbase_name <docbasename> -user_name <username> -action start


  • Alain Molimard says:

    Nice resume.
    On option 5, do you know if there is a way to specifiy a node when running in an HA configuration (two IndexAgent)?



  • Deepinti Bhuwalka says:

    While searching a particular word “Foot” the webtop is throwing the below error. I did not get any error while searching the same string from DA. Have cleared the cache and tmp folder in the application server with a restart but that did not fix the issue. Any help on the issue will be appreciated.

    Started index server and index agent still facing same issue

    [DM_API_E_EXIST]error: “Document/object specified by 0901469080a692b1 does not exist.”

    After closing this window, press the Refresh or Reload button on your browser to continue.

    Stack Trace:

    DfIdNotFoundException:: THREAD: [ACTIVE] ExecuteThread: ‘4’ for queue: ‘weblogic.kernel.Default (self-tuning)’; MSG: [DM_API_E_EXIST]error: “Document/object specified by 0901469080a692b1 does not exist.”; ERRORCODE: 100; NEXT: null

    at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(

    at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(

    at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getException(

    at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.checkForMessages(

    • Stephane Biehler says:

      Hi Deepinti,

      sorry for the late answer, maybe you can try the following:

      Check if the file exists in the Docbase:
      select * from dm_sysobject where r_object_id=’0901469080a692b1′;

      If it does exist, check if the object is indexed, you can login to the Dsearch web interface and search in the docbase’s data.

      Now, if the error, comes only when you search in Webtop and not in DA that means it tries to do something with this file, and if the file doesn’t exist anymore that means it’s cached somewhere. Can you tell me what king of document is it?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Stephane Biehler
Stephane Biehler