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. 'A database error occurred. Unable to find patron name' error when searching for patron in Voyager Circulation

    'A database error occurred. Unable to find patron name' error when searching for patron in Voyager Circulation

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Symptoms
    2. Defect Status
    3. Replication Steps
    4. Workaround
    • Product: Voyager
    • Product Version: 8.2.0-10.1.0
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

    Symptoms

    • 'A database error occurred. Unable to find patron name' error in Voyager Circulation when searching for patron
    • Patron cannot log into WebVoyage

    Defect Status

    Issue VYG-7636 (Fines of >21474836.47 prevents viewing patron in Circulation, WebVoyage) is currently in Development

    Replication Steps

    1. Create a patron and give them a fine of $5 (or make sure that the Circulation policy governing this transaction is set to include a Lost Item Processing fee >0)
    2. Create an item record and in the price field, enter any value greater than or equal to 21474836.47 (any value higher than this will change to 21474836.47 if you close the item and then re-open it)
    3. Charge the item to a patron
    4. Modify the due date to a date far enough in the past that this item will be flagged as Lost
    5. Run Circjob 12 to flag the item as Lost and create the Lost Item Replacement Fee (which will be the item's price from step 2) on the patron's record 
    6. Go back to Circulation and search for this patron; there will be an error stating 'A database error occurred. Unable to find patron name'; the patron will also be unable to log into WebVoyage

    Workaround

    Contact Voyager Support for assistance

     

     


    • Article last edited: 04-Dec-2019
    View article in the Exlibris Knowledge Center
    1. Back to top
      • 'A database error occurred while attempting to store request' error when placing call slip request in Voyager Circulation
      • 'ORA-01455: converting column overflows integer datatype' when running Pfpc save
    • 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