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. Primo extract from voyager generates logging errors

    Primo extract from voyager generates logging errors

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Additional Information
    • Article Type: General
    • Product: Voyager
    • Product Version: 8.2.0

    Problem Symptoms:
    *Running Pprimoexp.pub returns errors, but still runs successfully.

    Cause:
    This behavior is the result of Issue 16384-21537 / VYG-4635.

    Resolution:
    Issue VYG-4635 is resolved for Voyager 9.1.0 and higher.

    Additional Information

    Replication steps:
    1. Run /m1/voyager/xxxdb/sbin/Pprimoexp.pub
    2. The job will still run, but return these errors:
    log4j:WARN No appenders could be found for logger (com.exlibris.util.ThreadsafeDateFormatter).
    log4j:WARN Please initialize the log4j system properly.
    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

    Category: Interoperability (Voy)

    Subject: Primo (Voy)


    • Article last edited: 10/17/2014
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Primo extract does not extract titles of media items when discharged
      • Primo Extract is taking a long time after loading a large Voyager authority file
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Voyager
    2. Tags
      1. voy-resolved-9
    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