[OPEN-ILS-DEV] ***SPAM*** RE: ***SPAM*** RE: ***SPAM*** RE: ***SPAM*** Re: ***SPAM*** New Server/Upgrade from 1.4 to 1.6

[Soulliere, Robert]

Hi Adam,

I believe that is related to the tsearch2 module and migrating data from postgresql 8.2 to postgresql 8.3.

1)  review the information from the Postgresql documentation regarding tsearch2:
http://www.postgresql.org/docs/8.3/interactive/tsearch2.html


2)  create your new evergreen db and make sure you run these commands (from the Evergreen install instructions) before loading the data:
psql -f /usr/share/postgresql/8.3/contrib/tablefunc.sql evergreen
psql -f /usr/share/postgresql/8.3/contrib/tsearch2.sql  evergreen
psql -f /usr/share/postgresql/8.3/contrib/pgxml.sql     evergreen

This should ensure that you have the 8.3 versions of the various contrib modules including tsearch2 which is the cause of your pain.


3)  run step 4 from the installation instructions to create the evergreen schema.


4)  load your Evergreen data.

5) run:
psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/000.english.pg83.fts-config.sql evergreen

This sql preps your evergreen database for full text searching (using tsearch2) for Postgresql 8.3.


The order of the steps is very important.


Hope that helps.


I answered a question a while ago regarding upgrading from 8.2 to 8.3 and was thinking of adding a wiki page regarding upgrading fixing evergreen after a postgresql upgrade. However, I wasn't sure if this is the best way or if a built in script was being worked on to automate the postgresql 8.2 to 8.3/8.4 process and thus make these steps obsolete.

Please let if a wiki page with my steps for this would be helpful at this time and I will create it and link to it from the 1.4 to 1.6 upgrade instructions?


Thanks,
Robert




-----Original Message-----
From: open-ils-dev-bounces at list.georgialibraries.org [mailto:open-ils-dev-bounces at list.georgialibraries.org] On Behalf Of Adam Ray
Sent: Tuesday, May 18, 2010 12:51 AM
To: Evergreen Development Discussion List
Subject: [OPEN-ILS-DEV] ***SPAM*** RE: ***SPAM*** RE: ***SPAM*** Re: ***SPAM*** New Server/Upgrade from 1.4 to 1.6

OK so I have the new server up and have everything installed and I've come to the DB migration part.

Here's what I've tried:

Old$ pg_dump evergreen > evergreen.sql

New$ createdb -E UNICODE evergreen
New$ createlang plperl evergreen
New$ createlang plperlu evergreen
New$ createlang plpgsql evergreen
New$ createuser -P -s evergreen
New$ psql -d evergreen < evergreen.sql

When it gets to the line:

CREATE FUNCTION gtsq_in(cstring) RETURNS gtsq
    AS '$libdir/tsearch2', 'gtsq_in'
    LANGUAGE c STRICT;

I get this error:

NOTICE:  return type gtsq is only a shell
ERROR:  could not find function "gtsq_in" in file "/usr/lib/postgresql/8.3/lib/tsearch2.so"

Am I taking the wrong approach?

Thanks,
Adam



________________________________________
From: open-ils-dev-bounces at list.georgialibraries.org [open-ils-dev-bounces at list.georgialibraries.org] on behalf of Galen Charlton [gmc at esilibrary.com]
Sent: Thursday, May 13, 2010 2:41 PM
To: Evergreen Development Discussion List
Subject: Re: [OPEN-ILS-DEV] ***SPAM*** RE: ***SPAM*** Re: ***SPAM***    New     Server/Upgrade from     1.4     to 1.6

Hi,

On May 13, 2010, at 3:25 PM, Adam Ray wrote:
> One of the biggest problems we are having with the old installation is we have records we can look up by TCN, but won't show up in searches either in the staff client or OPAC.

Trying the procedure to reingest (i.e., reindex) bib records may help with that:

http://evergreen-ils.org/dokuwiki/doku.php?id=scratchpad:random_magic_spells#reingesting_bib_records

> Regarding the DB upgrade scripts, where would I find the procedures for that?

http://evergreen-ils.org/dokuwiki/doku.php?id=upgrading:evergreen:1.4_to_1.6

Regards,

Galen
--
Galen Charlton
VP, Data Services
Equinox Software, Inc. / Your Library's Guide to Open Source
email:  gmc at esilibrary.com
direct: +1 352-215-7548
skype:  gmcharlt
web:    http://www.esilibrary.com/


This E-mail contains privileged and confidential information intended
only for the individual or entity named in the message.  If the reader
of this message is not the intended recipient, or the agent responsible
to deliver it to the intended recipient, you are hereby notified that
any review, dissemination, distribution or copying of this communication
is prohibited.  If this communication was received in error, please
notify the sender by reply E-mail immediately, and delete and destroy
the original message.