[Koha] urx.chr error in upgrade from 2.2 to 3.0 zebra problems

Galen Charlton galen.charlton at liblime.com
Wed Mar 5 01:00:00 NZDT 2008


Hi,

There are two separate issues going on.

On Tue, Mar 4, 2008 at 12:32 AM, Pauley <pdavis at lyncs.org> wrote:
>  20:36:50-03/03 zebrasrv(5060) [warn] Failed to read character table urx.chr
>  20:36:50-03/03 zebrasrv(5060) [warn] urx.chr [No such file or directory]

The file that Zebra is looking for would have rules for indexing URLs.
 This is a minor error, i.e., you can continue testing your Koha 3
installation after you fix the problem below, but I will go ahead and
add the missing file to git.

>  20:36:50-03/03 zebrasrv(5060) [warn] Record didn't contain match fields in
>  (bib1,Local-number)
>  20:36:50-03/03 zebrasrv(5060) [log] error grs.xml <no file> 0

Since you're upgrading from 2.2.9 to 3.0, I suspect that your
biblionumber and biblioitemnumber are stored in 090$c and 090$d, which
Koha 3 expects by default to be in the 999 $c and $d.  To tell Zebra
this, go to the directory where you installed the Koha and Zebra
configuration files and edit
zebradb/marc_defs/marc21/biblios/record.abs.  Comment out the
following lines

melm 999$c      Local-Number:n,Local-Number:w,Local-Number:s
melm 999$d      biblioitemnumber:n,biblioitemnumber:w,biblioitemnumber:s

and add

melm 090$c      Local-Number:n,Local-Number:w,Local-Number:s
melm 090$d      biblioitemnumber:n,biblioitemnumber:w,biblioitemnumber:s

Then restart your Zebra server and try running rebuild_zebra.pl.  For
now, you may also want to edit your MARC frameworks to have
biblioitems.biblioitemnumber and biblio.bilionumber be copied to the
090 for new records that you add.

It looks like there should be a 22_to_30 upgrade script for moving the
090 to 999 for MARC21 databases -- I will add this as well.

Regards,

Galen
-- 
Galen Charlton
Koha Application Developer
LibLime
galen.charlton at liblime.com
p: 1-888-564-2457 x709


More information about the Koha mailing list