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. How do I determine if an Oracle Tablespace Extension is needed?

    How do I determine if an Oracle Tablespace Extension is needed?

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Question
    2. Answer
    3. Additional Information
    • Product: Voyager
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Question

    How to determine if an Oracle Tablespace Extension is needed?

    Answer

    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

     

    You may see errors in the Voyager clients that look like this:

    • 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."

    If you suspect you need a Tablespace extension, contact Support.

    Additional Information

    In Voyager, each Voyager instance has its own Oracle schema, which logically stores its data in a single Oracle tablespace, all of which have the same name (xxxdb or XXXDB). That tablespace physically stores the data in one or more datafiles. For optimal performance (and to avoid hitting the OS's limit on file size), we cap these files at 4 GB and create new ones as they are needed. However, that creation of new files is not automatic. 


    • Article last edited: 12-Apr-2020
    View article in the Exlibris Knowledge Center
    1. Back to top
      • How do I create an exclude file for a marcexport job?
      • How do I determine if keyword regen is needed?
    • 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