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. Unicode characters not displaying correctly for Oracle ODBC 19c drivers in Voyager Prepackaged Access Reports

    Unicode characters not displaying correctly for Oracle ODBC 19c drivers in Voyager Prepackaged Access Reports

    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
    5. Additional Information
    • Product: Voyager
    • Product Version: All
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare

     

    Symptoms

    Unicode characters when using the experimental (now available from Support) Oracle ODBC 19c drivers are not displaying correctly in Voyager Prepackaged Reports (PPR), regardless of the presence of the Arial Unicode MS font on the computer, and the NLS_LANG key in the PC's Registry being set to AMERICAN_AMERICA.US7ASCII, and regardless of the utf8to16 expression being used in the SQL.

    Defect Status

    VYG-7667 is in Development.

    Replication Steps

    1. Install Oracle ODBC 19c drivers (available from Support).
    2. Import bib record with diacritics.
    3. Use SQL code that utilizes utf8to16 function expression to pull up this record in Prepackaged Access Reports and display field with diacritics.
    4. Note that Unicode characters do not display properly.
    5. Unicode characters do display properly in Cataloging module and in WebVoyage.

    Workaround

    Continue to use the 10g Oracle Client on 32-bit Access systems.

    Additional Information

    Unicode characters do not display properly whether or not the utf8to16 function expression is used in the SQL.

    The 19c Oracle ODBC drivers for 64-bit Access are experimental and not supported for customer use with the understanding that non-Latin characters and diacritical markings will not display properly.

    For information about the AMERICAN_AMERICA.US7ASCII Registry setting change see:  How to resolve Error 12001 when running query in Prepackaged Reports?


    • Article last edited: 18-May-2020
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Unexplained expenditures show in ledger/fund display as well as fund transaction table in Voyager
      • Unicode formatting characters do not validate with MARC21 character set validation enabled
    • 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