Skip to main content
ExLibris

Knowledge Assistant

BETA
 
Voyager

 

Ex Libris Knowledge Center
  1. Search site
    Go back to previous article
    1. Sign in
      • Sign in
      • Forgot password
  1. Home
  2. Voyager
  3. Knowledge Articles
  4. UTIL: Cannot run keyword regen: "An index regen is currently running for xxxdb"

UTIL: Cannot run keyword regen: "An index regen is currently running for xxxdb"

  1. Last updated
  2. Save as PDF
  3. Share
    1. Share
    2. Tweet
    3. Share
  1. Symptoms
  2. Cause
    1. Resolution

Symptoms

  • Running a keyword index regen using the UTIL menu results in error: "An index regen is currently running for <xxxdb>" (where xxxdb is the Voyager Database Instance)
  • Cause

This issue is due to a previous regen not properly completing, resulting in the process id file for the previous regen being left in place, causing the subsequent regen to infer that the previous regen has not been completed.

Resolution

Delete the regen pid file "regen_running" from the previous regen:

 

  1. Locate the file for the previous regen. This file will be located at /m1/voyager/utility/<Voyager version #>/XXXdb/regen_running
  2. Ensure that the regen is not running by running: "ps -f -p $(cat regen_running)"
  3. If no regen is running delete the file ("rm regen_running")
  4. Rerun the regen using util.
View article in the Exlibris Knowledge Center
  1. Back to top
    • Using VIK to apply Oracle PSU to local environment
    • Vendor Account specified in import rule not added to order during import
  • Was this article helpful?

Recommended articles

  1. Language
    English
  2. Tags
    This page has no tags.
  1. © Copyright 2025 Ex Libris Knowledge Center
  2. Powered by CXone Expert ®
  • Term of Use
  • Privacy Policy
  • Contact Us
2025 Ex Libris. All rights reserved