CAT: "Unable to delete record" but record is deleted
- 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
- Use BulkImport to import bib record.
- Open bib record in Cataloging.
- Record > Delete.
- Receive message: "Unable to delete record"
- 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}
- Close record.
- Attempt to open record again (via Record > Retrieve by record ID > Bibliographic ... )
- 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