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. Save existing record to database in Cataloging gives error: "Unable to update this record."

    Save existing record to database in Cataloging gives error: "Unable to update this record."

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Problem Symptoms
    2. Cause
    3. Resolution
    4. Additional Information
    • Article Type: General
    • Product: Voyager

     

    Problem Symptoms

     

    • In Cataloging client, saving an existing record to database produces "Unable to update this record."
    • In Cataloging client, saving a new record to database produces "Unable to add this record."
    • In Acquisitions client, saving an existing record to database produces "Unable to update this record."
    • In Acquisitions client, saving a new record to database produces "Unable to add this record."

    unable to add this record.jpg

    Cause


    Keyword regen needed and/or database tablespace extension needed.
     

    Resolution


    Use the following "Additional Information" to determine if your sever needs a keyword index regen and/or a tablespace extension.

    Please contact Voyager Support as needed for assistance.

     

    Additional Information


    To determine if you require a keyword index regen, see this article: How do I determine if keyword regen is needed?

     

    If a tablespace extension is required, there will be recent ORA-1654 errors in the Oracle alert_VGER.log log file that will look something like the following (note that elevated access is required to view this log):

    ORA-1654: unable to extend index XXXDB.HEADING_UPDATE_DATE_IDX by 128 in tablespace XXXDB
    ORA-1654: unable to extend index XXXDB.HEADING_UPDATE_DATE_IDX by 1024 in tablespace XXXDB

    There can also be related ERROR entries in the log.voyager file that may look something like this:

    catsvr[16963] - THEWORKS - Wed Sep 18 15:52:25 2013
    - SQLError - search_sql__ppc.cxx[157]
    Function code: 3 query="insert into bib_index (bib_id, index_code, normal_heading,display_heading) values (:recids, :idxcodes, :normheads, :dispheads)"
    catsvr[16963] - ERROR - Wed Sep 18 15:52:25 2013
    - recordindex::ProcessData - recordindex.cpp[384]
    Index save failure - recid=1891857
    catsvr[16963] - ERROR - Wed Sep 18 15:52:25 2013
    - indexbuilder::Execute - indexbuild.cpp[146]
    Bib Index execute/update failure - scode= bibid=1891857
    catsvr[16963] - ERROR - Wed Sep 18 15:52:25 2013
    - UpdateBibRec - catalog.cpp[1190]
    Bib record update failure. Bibid=1891857

    Please open a Case with Support if you suspect you need a Tablespace extension. Support is also happy to do a keyword regen for you. Please open a Case.

    Category: Cataloging


    • Article last edited: 10/8/2019
    View article in the Exlibris Knowledge Center
    1. Back to top
      • SA/Circ: Incorrect due time for hourly/minutely loan on exception date
      • Saving BulkImport rule causes "Database Error. Return Code -1400"
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    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