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

    Clarification on p_manage_36 process

    • Article Type: General
    • Product: Aleph
    • Product Version: 16.02

    If there are duplicated records in the input file for p_manage_36, the service does not detect them as duplicates.

    In our case we have 3 duplicate records in the input file, that have the same single match in the database.
    This results in Output file 2 with the same record (same sys number) repeated three times and separated by a line:
    000000000 00000 0 00000
    Then if we load it with p-manage-18, it creates 3 duplicated records in database.

    The p-manage-36 service only detects duplicate records between input file and database, and not within the input file itself.
    If there are duplicate records in the input file, p-manage-36 will compare them one-by-one, and will write the sys no of the matching single record in database to the Output file 2.
    The line "000000000 00000 0 00000" separates between the records, thus preventing p-manage-18 from loading all the duplicated records as one, resulting in duplicated fields.
    The Output file 2 should be loaded by p-manage-18 with option Merge or Replace.

    You can use p-manage-38 (Merge records) service before the load, and then load its output with p-manage-18.

    Additional Information

    match, manage-36, merge

    • Article last edited: 10/8/2013