Use these instructions to stop a running index agent or start an index agent that is stopped.
An index agent that is disabled cannot be started and is not started automatically when its associated Content Server is started. You must enable the index agent before starting it. For information on enabling a disabled index agent, refer to Enabling index agents. If the index agent’s status is Not Responding, examine the machine on which it is installed and ensure that the software is running.
Stopping the index agent interrupts full-text indexing operations, including updates to the index and queries to the index. An index agent that is stopped does not pick up index queue items or process documents for indexing.
To start or stop an index agent:
Connect to the repository as a user who has system administrator or superuser privileges.
Navigate to Administration > Indexing Management > Index Agents and Index Servers.
Select the correct index agent.
To start the index agent, select Tools > Start.
To stop the index agent, select Tools > Stop.
Confirm that you want the index agent started or stopped.
The index agent’s status changes to running or stopped.
If the Content Server is in a projected to dormant state, then starting or stopping the index agent works correctly. However, if the Content Server is in a dormant state, then starting or stopping the index agent using Documentum Administrator does not work correctly. The status of the index agent appears as Not Responding. The index agent logs contain the following error: [DM_INDEX_AGENT_UNEXPECTED_DFC_EXCEPTION] Unexpected DfException: context: Init Connector cause: [DM_SESSION_E_OP_DISALLOWED_IN_STATE_UNLESS_ENABLED]error: "The operation (Opening a new transaction) is disallowed when the server is in Dormant state unless enabled by Data Center Managers on their sessions."