Index Text

• To re-index the text fields in your entire dataset, use the Content Manager Enterprise Studio Index Text command.

• To re-index only a selected set of objects, records or record titles, use the Content Manager client right-click Reindex option. For information about how to use this function, see the Content Manager client Help file.

1. Click to expand Datasets and right-click your dataset

   CAUTION: Do not use Index Text more than once at the same time. To prevent multiple users running concurrent word indexing processes, the Content Manager administrator should use Content Manager only on one computer and allow one word indexing process to finish before starting another one.

   NOTE:

   For Oracle databases only. The indexing option instructs Oracle's SQL *Loader (SQLLDR.EXE) utility to load the data files created straight into the Oracle data files instead of issuing standard SQL Insert Statements. This action can be less taxing on the target database. There are exceptions for when not to use this option. Refer to Oracle’s own online documentation for SQLLDR https://docs.oracle.com/database/122/SUTIL/oracle-sql-loader.htm#SUTIL3311

   If your version of Oracle does not have SQL *Loader installed, or it is called by a different name, the indexing process will not work. Check it is installed and named correctly before completing this process.

2. On the Utilities menu, click Word Index.

   A message advises you how many servers are currently using the dataset and that nobody should use the dataset while the function is running.

   The Word Reindexing Tool dialog box appears.

3. Select the objects and fields to re-index:
   • Record Titles
   • Record Notes
   • Record Additional Fields - use the Select button to determine the additional fields that get re-indexed and those that are excluded from the re-index.
   • From: and To: - find records in a given number range and index them, including title, notes and additional text fields.
   • Not Indexed Records - select to index records that have not been indexed.
   • Show Not Indexed Records - find the not indexed records and index them, including title, notes and additional text fields.
   • Classifications
   • Schedules
   • Thesaurus Terms
   • Communication Addresses
   • Location Addresses
   • Workflows
   • Activities
   • Additional Fields for other objects - use the Select button to determine the additional fields that get re-indexed and those that are excluded from the re-index.
   • Path for BULK INSERT work files - defaults to Bulk Loader path that was specified for this dataset in its properties' Options tab. Must be a UNC path. If there is no path specified in the Options tab, this field is blank, as well and the function still works as intended. See Options dialog box.
   • Working Directory - the working directory that is the target of the transaction batch files for the indexing process.

     The working directory is a folder that Content Manager uses to build the indexes, and the path in this field should be a UNC path to ensure the server with the relational database can access it.

     NOTE:

     The account that your database service (e.g. SQL Server, Oracle) is running under must have full access (read, write and delete) to this UNC path directory.

     If you are experiencing any issues when using this path, you may want to try the following:

     • To avoid DNS issues, using the IP address of the server hosting the UNC path directory, for example, \\10.0.0.1\path instead of \\myserver\path
     • Using the server that is running the database service to host the UNC path directory
     • Modifying or turning off anti-virus software or firewalls on the computers involved

   • Drop and restore indexes as part of the indexing process - select to make the indexing process faster
   • Drop and restore constraints as part of the indexing process - select to make the indexing process faster
4. Click OK to start the re-indexing process.

   A message advises you when a log file SQLCommands_<DB ID>.txt already exists.

5. Click OK to overwrite it.

   Another message advises you that Content Manager has broadcast a message to all logged on users that maintenance is in progress and will not allow users to log on to the database.

Content Manager displays a message when re-indexing is complete.