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

    Records written to error file also imported into database

    • Article Type: General
    • Product: Voyager
    • Product Version: 8.2.0

    Problem Symptoms:
    * Errors logged in log.imp* during bulk import for records with non-Unicode characters
    * Records written to error file, but also imported

    This behavior is the result of a defect in Voyager 8.2.0.

    Versions other than Voyager 8.2.0 will not be impacted by this defect.

    Additional Information

    Replication steps:
    1. Create import rule in System Administration > Cataloging > Bulk Import Rules for a set of records with MARC21 MARC-8 encoding.
    2. Import a file of MARC21 MARC-8 encoded records, where some records have non-convertible characters, using rule from step 1.
    3. Review the log and note that errors are written to the log for these records, as expected. For example:
    : ERROR: Unparseable record written to error file: [22]-680 : c->8 undefined char in page 0 at 138 'ceb13720 ..7 '
    4. Note that record is also written to err.imp.{datestamp} file.
    5. Search for one of the records in the error file in Cataloging. Note that the record has also been imported.

    Additional information: More information on running Bulk Import and the files it produces available in Technical User's Guide.

    Category: Batch jobs - Voyager

    Subject: Voyager

    • Article last edited: 1/6/2015