Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    BULK: Bi-Directional merge fails on Linux

    • Article Type: Known Issue
    • Product: Voyager
    • Product Version: 7.2.4
    • Relevant for Installation Type: Total Care; Dedicated-Direct; Direct; Local

    Symptoms

    * In Cataloging, when bi-directional merge is attempted, run-time errors 440/65099 given immediately, and client closes.
    * When bulk import attempts to apply bi-directional merge, the process produces errors & dies.

    Defect Status

    Issue 16384-15585 resolved for Voyager 8.1.1 and higher.

    Additional Information

    Replication steps:  

    1. System Administration > bibligraphic duplicate detection > create profile that will bi-directional merge.
    2. Add the profile to your Cataloging Policy Definition, and also to a bulk import rule.
    3. Make sure you have records (or create them) in the database that will win the quality hierarchy you set up over records that you will be merging them with.
    4. Import one of the records that should be bi-directional merged; get run-time errors 440 and 65099.
    5. Place same file of records on the server and attempt a bulk import. Receive errors and the process is terminated without merging records.

    Other information:  Merge functionality works fine; bi-directional merge appears to be the only thing having trouble.

    Category: Batch jobs


    • Article last edited: 3/2/2015
    //doorbell.io feedback widged