[Koha-bugs] [Bug 30896] New: Running misc/batchRebuildBiblioTables.pl -c fails with error "Running Data too long for column 'lccn'"

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30896

            Bug ID: 30896
           Summary: Running misc/batchRebuildBiblioTables.pl -c fails with
                    error "Running Data too long for column 'lccn'"
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: System Administration
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: david at davidnind.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

The command line script misc/batchRebuildBiblioTables.plcommand is used after
updating Koha to MARC mappings (Administration > Catalog > Koha to MARC
mappings).

Running misc/batchRebuildBiblioTables.pl -c from the command line (to rebuild
the Koha to MARC mappings) with the sample data in koha-testing-data generates
this error message:

C4::Biblio::_koha_modify_biblioitem_nonmarc(): DBI Exception: DBD::mysql::st
execute failed: Data too long for column 'lccn' at row 1 at
misc/batchRebuildBiblioTables.pl line 71

To replicate (when using koha-testing-docker and the sample data):

1. From the command line run ./misc/batchRebuildBiblioTables.pl -c
2. Error occurs:
   C4::Biblio::_koha_modify_biblioitem_nonmarc(): DBI Exception: DBD::mysql::st
execute failed: Data too long for column 'lccn' at row 1 at
misc/batchRebuildBiblioTables.pl line 71

I identified this when testing bug 30850 (I worked around the issue by using
Tools > Batch item modification to delete the LCCN data in 010: created report
to list all the record numbers, added MARC modification templates to delete
fields 010 $8 $a $b $z, ran batch record modification).

I'm not sure whether this is a problem with the table structure, or whether in
real life you would have to identify and fix the problematic data for 010.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.