Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform administration
Table of Contents
Choose your release version
    Home Paris Now Platform Administration Now Platform administration Search administration Zing text indexing and search engine Zing indexes words Regenerate a corrupt index

    Regenerate a corrupt index

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Regenerate a corrupt index

    Typically, a corrupt index regenerates itself. If the system does not start the regeneration process, you must issue a script command to delete the existing index and regenerate it.

    Procedure

    1. Navigate to System Definition > Scripts - Background.
    2. In Run Script box, type the syntax for the background script:
      To regenerate the task text index, the following could be used as a background script:
      var indexer = new GlideLuceneTextIndexEvent();
         indexer.createIndex("task", "my_email@service-now.com");
      

      Change the email address to the address that receives the notification when the index is completed. The script creates an event that the index handler processes so the script completes almost instantly.

    3. Click the Run script button.
    4. When the scheduled job picks up the event, you can check the Component Status page and see that the index is being generated. An entry also appears in the log, as shown in the following example:
       10/28/09 15:36:19 (521) worker.1 worker.1 TextIndexGenerator: Text index generation starting for: task
      

    Result

    As each extended table completes, it is logged:
     10/28/09 15:37:13 (213) worker.1 worker.1 [0:00:01.462] TextIndex generation complete for: problem, rows indexed: 11
    After all the extended tables are completed, the Component Status page entry is updated to "completed" and a final log entry is made. The log entry shows how long the process took.
      10/28/09 15:37:20 (794) worker.1 worker.1 TextIndexGenerator: Text index generation complete for: task, in: 0:01:02.669
    
    Related tasks
    • Enable text indexing for a table
    • Configure a single table for indexing and searching
    • Configure multiple tables for indexing and searching
    • Regenerate a text index for a table
    • Remove an index
    • Remove an index for a specific field
    • Remove an index for a child table
    • Change the query mode of an indexed table
    • Configure tables to use the Japanese tokenizer
    Related concepts
    • Zing indexes punctuation as part of some words
    • Zing indexes some HTML elements
    Related reference
    • Zing index and search dictionary attributes
    • Text indexing statistics and status

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Regenerate a corrupt index

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Regenerate a corrupt index

      Typically, a corrupt index regenerates itself. If the system does not start the regeneration process, you must issue a script command to delete the existing index and regenerate it.

      Procedure

      1. Navigate to System Definition > Scripts - Background.
      2. In Run Script box, type the syntax for the background script:
        To regenerate the task text index, the following could be used as a background script:
        var indexer = new GlideLuceneTextIndexEvent();
           indexer.createIndex("task", "my_email@service-now.com");
        

        Change the email address to the address that receives the notification when the index is completed. The script creates an event that the index handler processes so the script completes almost instantly.

      3. Click the Run script button.
      4. When the scheduled job picks up the event, you can check the Component Status page and see that the index is being generated. An entry also appears in the log, as shown in the following example:
         10/28/09 15:36:19 (521) worker.1 worker.1 TextIndexGenerator: Text index generation starting for: task
        

      Result

      As each extended table completes, it is logged:
       10/28/09 15:37:13 (213) worker.1 worker.1 [0:00:01.462] TextIndex generation complete for: problem, rows indexed: 11
      After all the extended tables are completed, the Component Status page entry is updated to "completed" and a final log entry is made. The log entry shows how long the process took.
        10/28/09 15:37:20 (794) worker.1 worker.1 TextIndexGenerator: Text index generation complete for: task, in: 0:01:02.669
      
      Related tasks
      • Enable text indexing for a table
      • Configure a single table for indexing and searching
      • Configure multiple tables for indexing and searching
      • Regenerate a text index for a table
      • Remove an index
      • Remove an index for a specific field
      • Remove an index for a child table
      • Change the query mode of an indexed table
      • Configure tables to use the Japanese tokenizer
      Related concepts
      • Zing indexes punctuation as part of some words
      • Zing indexes some HTML elements
      Related reference
      • Zing index and search dictionary attributes
      • Text indexing statistics and status

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login