sl => lsmb

[david <..hidden..>]

I have no trouble setting up LSMB... good instructions, no problems. The problem 
is importing SL data. The SL installation continues to work perfectly, and I've 
dumped the data from SL using it's internal backup function.

This is postgresql 8.3, LSMB 1.2.16 new install. SL 2.6,27
Connects to admin.pl correctly.


ledgersmb=> \i /home/david/2008-2.6.12-20080910.sql     <SL dataset backup>

ledgersmb=> \i /usr/local/ledgersmb/sql/legacy/Pg-upgrade-2.6.12-2.6.17.sql

ledgersmb=> \i /usr/local/ledgersmb/sql/legacy/Pg-upgrade-2.6.17-2.6.18.sql
	LOTS of errors so must be wrong - see below.


The UPGRADE instructions suggest "correcting" ownership errors, but the messages 
are generic (above) and don't appear to be ownership problems.

There is a shell script (sl2ls.sh) which looks like it's supposed to run the 
upgrade scripts, but none of the docs suggest actually using it.


ABBREVIATED TRANSCRIPT OF WHAT I DID (in psql):

ledgersmb=# \i /home/david/2008-2.6.12-20080910.sql
< snip usual stuff >
ledgersmb=# select version from defaults;
 version
---------
 2.6.12
(1 row)

ledgersmb=# \i /usr/local/ledgersmb/sql/legacy/Pg-upgrade-2.6.12-2.6.17.sql
psql:/usr/local/ledgersmb/sql/legacy/Pg-upgrade-2.6.12-2.6.17.sql:1: ERROR: 
relation "session_session_id_seq" already exists
psql:/usr/local/ledgersmb/sql/legacy/Pg-upgrade-2.6.12-2.6.17.sql:8: ERROR: 
relation "session" already exists
ALTER TABLE
ALTER TABLE
UPDATE 40055
ALTER TABLE
ALTER TABLE
UPDATE 1
ledgersmb=# \i /usr/local/ledgersmb/sql/legacy/Pg-upgrade-2.6.17-2.6.18.sql

< snip lots of stuff including MANY errors as follows >

psql:/usr/local/ledgersmb/sql/legacy/Pg-upgrade-2.6.17-2.6.18.sql:288: ERROR: 
current transaction is aborted, commands ignored until end of transaction block
ROLLBACK
ledgersmb=#


I know lots of others have successfull done this, so I guess the problem must be 
me, but any help would be gratefully received.

David.