Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    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. CAT: "Unable to delete record" but record is deleted

    CAT: "Unable to delete record" but record is deleted

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Problem Symptoms
    2. Defect Status
    3. Replication steps
    4. Workaround
    5. Additional information
    • Article Type: General
    • Product: Voyager
    • Product Version: 9

    Problem Symptoms

    • Bib record imported via BulkImport without using -KADDKEY
    • Attempt to delete bib record from Cataloging results in message "Unable to delete record"
    • When attempt to find record again after receiving message, record is not there - has actually been deleted

    Defect Status

    Issue VYG-5540 is resolved in Voyager 9.1.0

    Replication steps

    1. Use BulkImport to import bib record.
    2. Open bib record in Cataloging.
    3. Record > Delete.
    4. Receive message: "Unable to delete record"
    5. log.voyager shows errors:

    keysvr[28402] - ERROR - Tue Jun 10 14:19:37 2014
    - turbobibtext::Delete - turbo_bt.cpp[785]
    Could not delete/overwrite bibtext entry for - {bib_id}
    keysvr[28402] - ERROR - Tue Jun 10 14:19:37 2014
    - keywordsearch::update - keyword.cpp[1346]
    Bibtext delete failure - bibid={bib_id}
    catsvr[28352] - ERROR - Tue Jun 10 14:19:37 2014
    - keyindex::Execute - keyindex.cpp[351]
    Keyword update request failed.
    catsvr[28352] - ERROR - Tue Jun 10 14:19:37 2014
    - indexbuilder::Delete - indexbuild.cpp[179]
    Bib Index delete failure - scode=GKEY bibid={bib_id}

    1. Close record.
    2. Attempt to open record again (via Record > Retrieve by record ID > Bibliographic ... )
    3. Receive message: "Record {bib_id} not found or unable to display it."

    Workaround

    Keyword index records via BulkImport with -KADDKEY or via keyword regen before deleting records from database. See "BULK: Records are not keyword indexed" and "Who can run a keyword regen?")

    Additional information

    When record is deleted, data remains in BIB_TEXT and BIB_HEADING, as well as in the counts for STAFFBIBS and OPACBIBS in the HEADING table. Data can be resolved with regens; open Case via Support Portal to request regens.


    • Article last edited: 11-Jun-2014
    View article in the Exlibris Knowledge Center
    1. Back to top
      • CAT: "Print Selected" prints MFHD Loc for Item Perm Loc
      • CAT: "Unable to save record" after replacing auth
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      1. voy-resolved-9
    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