Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Voyager
    Ex Libris Knowledge Center

    Circjob 43:error in log if local call slip is processed

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Voyager
    • Product Version: 7.2.5

    Description:
    Bug Report Form for Issue 16384-16321

    Module(s): Circjob
    Server platform(s) affected: Solaris/all
    PC OS (if applicable): n/a
    Browser & version (if applicable): n/a
    Release(s): reported in 7.2.5; replicated in 8.0

    Expected results: Circjob 43 should reflect accurate error messaging in the log and correctly process patron data for all stub databases to which it can successfully connect.

    Actual results: If a patron with stubs also has a processed local call slip request at the time circjob 43 is run, the job will write ‘Error: Unable to collect data for this patron record. Possibly due to failure to communicate with remote database LOCAL. Circjob log error message:’, and won’t process any of the stub data.

    Workflow implications: Some data won’t be updated by circjob 43.

    Replication steps:
    Find a patron in db A that has a stub in db B.
    As this patron, place a local call slip in db A.
    Process the call slip.
    Run circjob 43 and check the log.ubsynch for the patron_id of your patron – you’ll see a message that says something like:

    ========== Patron ID 431 ==========
    Error: Unable to collect data for this patron record.
    Possibly due to failure to communicate with remote database LOCAL.
    Circjob log error message:

    Other information: If the call slip has been placed but not yet processed, the problem does not occur.

    Resolution:
    Fixed in Voyager 8.1.2

    • Article last edited: 10/8/2013