[OPEN-ILS-DEV] 1.4.0.4 -> 1.6.0.3 not a smooth upgrade: not seeing copy summaries

[Victoria Bush]

Dan, I did what you said, and I've written some of those notes below; however, I am not satisifed with how postgres 8.3 is installed, and I'd like to re-install it before I continue. I keep running into weird problems, and I think things are not well with postgres. 

An aside: the installation instructions for 1.4.0.4 said to install postgres 8.2 via stow, but the 1.6 and the upgrade instructions give no such help with regards to installing postgres 8.3 in such an environment. This seems to be part of my problem. I'm going to come back in tomorrow and try to do all this from scratch. 

However, if it is helpful, here is what I was able to see when I tried updating the database again from the 1.4.0.4 dump.......

On Mar 22, 2010, at 3:56 PM, Dan Scott wrote:

> On Mon, 2010-03-22 at 15:35 -0500, Victoria Bush wrote:
>> See below for updates.....
> 
> <snip>
> 
>> I have mine set to log to /home/postgres/logfile, so I found the following which leads me to believe that the problem is actually upgrading the databases from 1.4.0.4 to the 1.6 format. I see this for most statements: 
>> 
>>> ERROR:  schema "serial" does not exist
>>> ERROR:  schema "acq" does not exist
> 
> This is a huge problem. Part of the 1.4.0.5-1.6.0.0 upgrade script
> creates the serial and acq schemas inside a transaction; if these
> schemas don't exist, then the rest of the database schema will be in a
> very broken state.
> 
> I would suggest going back to one of your 1.4.0.4 backups and rerunning
> the 1.4.0.5-1.6.0.0 script again; send us the very first error that
> occurs during the upgrade.

 I blew away what was in postgres, reloaded the data from my dump file, and vacuumed the data as a precaution. 

When I try to run the 1.4.0.5-1.6.0.0 script again, these are the very first results from the script: 

> psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:19: ERROR:  schema "acq" does not exist
> psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:20: ERROR:  schema "serial" does not exist
> BEGIN
> INSERT 0 1
> psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:31: NOTICE:  CREATE TABLE will create implicit sequence "standing_penalty_id_seq" for serial column "standing_penalty.id"
> psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:31: NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "standing_penalty_pkey" for table "standing_penalty"
> psql:Open-ILS/src/sql/Pg/1.4.0.5-1.6.0.0-upgrade-db.sql:31: NOTICE:  CREATE TABLE / UNIQUE will create implicit index "standing_penalty_name_key" for table "standing_penalty"
> CREATE TABLE
> INSERT 0 1
> INSERT 0 1
> INSERT 0 1
> INSERT 0 1
> INSERT 0 1
> ......


The rest of the messages are notices exactly as shown above: implicit sequences, indices, etc. (The two errors here are supposedly complaining about trying to delete the schemas acq and serial, which don't exist in my 1.4.0.4 data.) When I look at the database after running this script, I do see schemas acq and serial. So they exist now.

Proceeding, I get this result when I run the script to go from 1.6.0.0 to 1.6.0.1:

> $ psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/1.6.0.0-1.6.0.1-upgrade-db.sql evergreen
> BEGIN
> INSERT 0 1
> CREATE FUNCTION
> ALTER TABLE
> psql:Open-ILS/src/sql/Pg/1.6.0.0-1.6.0.1-upgrade-db.sql:34: NOTICE:  ALTER TABLE / ADD UNIQUE will create implicit index "penalty_grp_once" for table "grp_penalty_threshold"
> ALTER TABLE
> CREATE FUNCTION
> UPDATE 1
> COMMIT
> psql:Open-ILS/src/sql/Pg/1.6.0.0-1.6.0.1-upgrade-db.sql:101: ERROR:  duplicate key violates unique constraint "i18n_locale_name_key"
> INSERT 0 1
> CREATE RULE
> INSERT 0 1
 
No errors were generated when upgrading to 1.6.0.2 or 1.6.0.3. 

Now, if I restart everything and run autogen.sh (which takes a few minutes to run completely), I get something odd: 

> $ ./autogen.sh -c /openils/conf/opensrf_core.xml -u
> Updating Evergreen organization tree and IDL using '/openils/conf/opensrf_core.xml'
> 
> Updating fieldmapper
> Updating web_fieldmapper
> Updating OrgTree
> Updating OrgTree HTML
> Updating locales selection HTML
> Updating Search Groups
> Can't use an undefined value as an ARRAY reference at org_lasso_js.pl line 30.




--
Victoria Bush
Opscan Evaluation Manager
Center for Teaching, Learning & Technology
vbush at ilstu.edu