Check out the documents here.
Monthly Archives: April 2009
Typically we would just use the remote desktop icon to remote into a server, or for the more command-line driven folks, a /mstsc at the run command prompt. I was told by tech support to actually use the following for windows server instead: /mstsc /console /v:[servername]
I don’t quite understand why, but it seems to have something to do with 1 single account. Please let me know if you’ve the exact explanation(s). No prize though.
- Remote into the content server machine
- Create a file called objects.api on c:\temp (or any directory you like); the file content shall be:
- #get all r_object_ids for dm_document type
- ?,c,select r_object_id from dm_document
- Then run the DOS command on content server
- iapi32 -U -P c:\ids.txt
- It will store all r_object_ids in the ids.txt.
Instead of using the API to send the objects for indexing, one-by-one, there is a simpler and more efficient way of doing things.
- Generate the list of r_object_id by this DQL:
- select r_object_id from dm_document
- Copy the list into a TXT file (filename: ids.txt)
- Save the TXT file @ :\Documentum\jboss4.2.0\server\DctmServer_IndexAgent1\deploy\IndexAgent1.war\WEB-INF\classes
- Once the resubmission is completed, the TXT file is renamed from: ids.txt >> ids.txt.done
Now, how do you actually get the list of r_object_id since the query potentially returns you millions of entries? Look out for the next post.
This DQL breaks down the failed items by type and user:
select name, task_state, count(*), item_type from dmi_queue_item where name in (‘dm_fulltext_index_user’, ‘dm_fulltext_index_user_01’) and task_state = ‘failed’ group by name, task_state, item_type order by name
You’ll need to modify the query accordingly for the “name” condition.
- Identify which content server the advance search will be sent to, e.g., server1
- Remote into the content server and launch iAPI
- Execute the following to turn on tracing:
- Go to Webtop to perform the advance search
- Go back to the content server and execute the following API command:
- Collect the log file @ W:\Documentum\dba\log\fulltext, filename is “fttrace_eRegistry.log”