[OPEN-ILS-GENERAL] Marc Export Script Error

[Ben Shum]

Hi Jesse,

Some questions for you... what version of Evergreen are you using with
that PostgreSQL 9.3 system?

That error you're seeing from the upgrade log sounds like maybe you
might not have your search_path set appropriately after the database
was copied over.  For example:  "After restoring a database, make sure
to reset the search_path accordingly with something like: alter
database unpredicable_haxxors_go_away set search_path = evergreen,
public, pg_catalog;"

As for that other error, Substr outside of string at
/usr/share/perl5/MARC/Record.pm line 573 ; my guess is that you have
some bad MARC records in your database.  This is likely unrelated to
your change in PostgreSQL, or maybe the version of MARC::Record that
you're now using is less tolerant?  Or maybe you were using the older
marc_export script before it was changed around 2.6 or so and it
somehow tolerated the bad MARC better.

In any case, I would check those bibs out on your system to determine
if there's any red flags in the way the MARC was created.  Maybe
there's something that doesn't conform to the "standard" and that's
making things unhappy.

-- Ben

On Tue, Jul 28, 2015 at 12:30 PM, Jesse McCarty <jessem at burlingtonwa.gov> wrote:
> Hi Everyone,
>
>
>
> I am working on a new Evergreen Server to deploy in the fall (Ubuntu 14.04,
> Postgres 9.3 – Current system is Ubuntu 12.04, Postgres 9.2) and am running
> into an error with the marc_extract script. The script works with no issue
> on the production system running Postgres 9.2, but after I import the
> current production data into a test server (identical to the current
> production server, with older DB data) and upgrade Postgres to 9.3 it stops
> working with the following error:
>
>
>
> Error in bibliographic record 168171
>
> Substr outside of string at /usr/share/perl5/MARC/Record.pm line 573
>
>
>
> There are two other bibliographic records that have the error as well
> (168498 & 172482).
>
>
>
> The new database seems to be working otherwise (attached is a screen shot of
> the output of the pg_upgradecluster results) even though the upgrade showed
> some errors.
>
>
>
> Any help is greatly appreciated. Thanks!
>
>
>
> Jesse McCarty
>
> City of Burlington
>
> IT Technical Assistant
>
>



-- 
Benjamin Shum
Evergreen Systems Manager
Bibliomation, Inc.
24 Wooster Ave.
Waterbury, CT 06708
203-577-4070, ext. 113