[OPEN-ILS-DEV] (no subject)

[Dan Scott]

On 15/10/2007, Grant Johnson <fgjohnson at upei.ca> wrote:
>
> Hey,
>
> Anyone know the correct syntax for loading the gutenburg records? and
> other rec.'s for that matter?
> On http://open-ils.org/dokuwiki/doku.php?id=evergreen-admin:importing:bibrecords
> when I get to the step running the sql script (# \i ~/gutenberg.sql) I get
> a load of errors.
> And the stdout ends with;
>
> psql:/home/evergreen-admin/gutenberg.sql:374485: invalid command \N
> psql:/home/evergreen-admin/gutenberg.sql:374508: invalid command \.
> psql:/home/evergreen-admin/gutenberg.sql:435383: ERROR:  syntax error at
> or near "Edward"
> LINE 1: Edward Gaylord Bourne (Annotator</subfield></datafield><data...
>
> Wife is calling me to bed now - I'll check logs in the AM.
> ver. 2.2.9, postgres, ubuntu
>
> Great to put some faces to names in Victoria.
> Cheers
>
>
> F. Grant Johnson
>   Systems Coordinator
>   Robertson Library
>   University of Prince Edward Island
>

Hi Grant:

Version 2.2.9? Hmm, any chance you've been playing with Koha recently? :)

I'm sure it is the right syntax, having run through the instructions with
Gutenberg and other records a few times now. I just ran through the
Gutenberg import process using OpenSRF trunk & Evergreen trunk, twice; the
first time I got similar complaints from PostgreSQL about the '\N' commands
when loading gutenberg.sql.

I then wiped the database with build-db.sh, ran VACUUM FULL to recover the
wasted database space, broke the file up into several separate COPY commands
wrapped in transactions (BEGIN; COMMIT;), and loaded the files in order to
try to reproduce the error in a more specific location of the file, and the
entire load succeeded without complaint.

Okay. So I wiped the database, ran VACUUM FULL again, and loaded the whole
thing as a single file. And once again, it succeeded without complaint. My
suspicion is that the transaction for the entire file reached some internal
limit for PostgreSQL exacerbated by the lack of vacuuming I had done in the
past, freaked out, and started spitting out errors. By running VACUUM FULL I
suspect I cleared up the condition that had caused the problem in the first
place.

So, Grant, try wiping your database, vacuuming it, and loading
gutenberg.sqlagain. You just might have success.

-- 
Dan Scott
Laurentian University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.georgialibraries.org/pipermail/open-ils-dev/attachments/20071016/0c6a24f8/attachment.html