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. After upgrade, read-only user cannot find table in Oracle.

    After upgrade, read-only user cannot find table in Oracle.

    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
    • Product: Voyager
    • Product Version: All
    • Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care

     

    Problem Symptoms

    • After upgrade, read-only user cannot find table in Oracle.
    • Query or describe table results in error:

    ERROR:
    ORA-04043: object "XXXDB"."[table name]" does not exist

    Cause

    This problem may occur if the read-only Oracle user needs to be rebuilt.

    Resolution

    If you are experiencing these symptoms, try rebuilding the read-only Oracle user. 

    If you are a TotalCare customer or would prefer Support do this, please open a Case via the Support Portal.

    Additional Information

    Instructions for rebuilding read-only user: Create & refresh Oracle read-only users for ODBC 

     


    • Article last edited: 02-Mar-2016
    View article in the Exlibris Knowledge Center
    1. Back to top
      • After migration to new server hardware unable to access Voyager clients or the OPAC
      • After upgrading from 7.x to 8.2.x, Primo Extract fails
    • 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