FTIntegrity is used to verify indexing after migration or to get a status after a normal indexing. The tool is a standalone Java program that verifies all types that are registered in the dmi_registry_table with the user dm_fulltext_index_user. By default, the utility compares the object ID and i_vstamp between the repository and xPlore. In this blog I will share with…
At a customer we encountered some issues with FT Search after documents migration. In fact, some documents were not indexed correctly or partially indexed, the need was to know which documents are impacted to resubmit the indexing again. The FTIntegrity tool is not able to give the needed result, so the only way was XQuery search. However, this blog is…
At a customer, I received an incident saying that on D2 a document is found by browsing and not found using normal search. The root cause seems to be easy: The Document isn’t indexed?! Not really, you will see it wasn’t easy to find 😉 1. Analysis When we have an issue to find a document, usually the problem is…
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…
At some of our customers, we often install new docbases for development purposes which are used only for a short time to avoid cross-team interactions/interferences and this kind of things. Creating new docbases is quite easy with Documentum but it still takes some time (unless you use silent installations or Docker components). Therefore installing/removing docbases over and over can be a…
