How to rebuild the FTS index on a Server Group ?

Legacy ID:KA425653
These steps are to perform a complete "clean" reindex.  This requires clearing out the current copy of the index.  In general, you can perform a reindex without executing all of these steps.  The extra steps are just to reindex in an environment where you do not trust the exiting collection files or simply want to start over with a completely new index.

In a Server Group, you may have more than one indexer server.  You will need to perform these steps for each indexer that needs to be reindexed.

Perform the following steps:

1- Stop AR Server service on the FTS Indexer server  (this is done to remove any locks that exist on the collection files

2- Erase all the files in Collection directory of the FTS Indexer server:
{Installation directory}/ARSystem/ftsconfiguration/collection
This directory can be different and is set in the Centralized Configuration under Full-Text-Collection-Directory

3- Delete all the records from the FT_PENDING table in the Database for this Indexer server.
Perform the following SQL script at the Database level to copy all contents from the existing FT_PENDING table to another table just as a backup in case it is required.
(Note: the backup data will not be used but just in case you are required to backup the data as per internal policies).

SQL Server:
select * into ft_pending_copy from ft_pending
delete from ft_pending where indexservername='<Server-Connect-Name of Indexer Server>'

Oracle:
create table ft_pending_copy as select * from ft_pending;
delete from ft_pending where indexservername='<Server-Connect-Name of Indexer Server>';
You may need to issue a commit

4- Start AR Server service

5- Perform reindexing from the Primary Indexer Server:
From the Remedy Management Console or the AR System Management Console, open the AR System Server Group Console and then the FTS Management Console.
Highlight the Indexer server name that you are working on. Then make sure that for the 'Reindex' selection field that you have "Server" selected.  Then click on "Reindex"

Note:  If you have more that one indexer server in an FTS HA environment, wait until the reindex from this server is complete before reindexing on other servers.  This way users can still perform FTS/MFS searches

6- Monitor whether reindex is performed. 
You can monitor the progress from the FTS Management Console/

You can also monitor progress from the database
To determine that the reindexing action is complete, monitor the FT_PENDING table for the operationType .

From a database client you can execute this SQL:
select count(*) from FT_Pending where indexservername='<Server-Connect-Name of Indexer Server>' AND (operationType = 5 or operationType = -5);

Also, check the Collection directory to observe that indexes files are being created.  Note that there is a separate directory for each indexed form (based on its schemaId)

7.  If using an FTS HA environment, perform these steps on the next indexer server

Note: While indexing takes place, users will be directed to another indexer server while performing searches when using HS FTS. If HA FTS is not used, users will get a message or no records being found.
Make sure users are aware that this may be temporary behavior if a reindex is taking place.

NOTE: This article is also available in Spanish, use the link below or search by Article Number 000165056. / NOTA: Este artículo también está disponible en Español, usar el siguiente enlace o buscar por el Número de Artículo 000165056
Remedy- FTS - Como reconstruir los Indices FTS en un Server Group