[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help on migrating from SL 2.6.1.5 to LS 1.1.12 - first login to system stalled on Upgrading to Version 1.1.12

On 5/31/07, ousseynou diagne <..hidden..> wrote:

Thank you Chris,

I am working on it, My boss who made some customization on our system
has already pointed me on that path to troubleshoot the issue. I was
able able to fix the issue relate to the Pg-upgrade-2.6.12-2.6.17.sql
script. the error was on table acc_trans  "Cannot drop table acc_trans
column amount because other objects depend on it".  As the Hint
suggested we  use Drop Cascade to drop all the views and rules that
depend on that table and It work.

After this I got error running the next script
Pg-upgrade-2.6.17-2.6.18.sql which is on the first line of the script
"ALTER TABLE chart ADD PRIMARY KEY (Id)  ERROR: mutiple primary keys for
table "chart" are not allowed. After checking our system I found that we
already have define a Primary key on our system for the chart table. the
same also has been done for the acc_table (added new column
ourcompanyname_id and made a primary key. So we have some work to do
here and I and consult my boss about what to do.


Ok.  Chances are you can just delete the offending lines from the
script if you already have the primary keys in place.  This may cause
problems for later updates (around the 1.4 timeframe), however.


In the meantime I want to know, if it is mandantory for the migration
from SL to LS to succeed, to change the owner of the database from
sql-ledger to ledger-smb user. I am asking this question because I was
not getting any error message (just a blank page with Upgrading to
Version 1.1.12)with sql-ledger as the owner of the database and tables.
Once I changed the owner of our database, tables, sequences and views to
ledger-smb  I start getting the errors messages which gave us some hints
of what the problem was.
My question is. Is it possible to keep sql-ledger  user as the owner of
db and tables. if yes how to tweak the system for that. If No what are
the implication for changing the db owner in regard  of the history,
previous transactions data integrity and consistency.


Sure.  The owner can be any user.  It is a good idea for that not to
be a superuser, however.

Best Wishes,
Chris Travers



Thank you


Chris Travers wrote:
> Hi;
>
> Try as follows:
>
> log into the db using psql.
> select version from defaults;
>
> Then run the SQL scripts one at a time from the version listed.  I.e.
> if it says 2.6.12, you start with the upgrade script starting with
> Pg-upgrade-2.6.12.
>
> The command to run the scripts is \i path/to/file inside psql.
>
> When you get an error, post that here.  Chances are that you have some
> sort of invalid data in your database.  We want to find out what sort
> of data bafore proposing a solution.
>
> Best Wishes,
> Chris Travers
>
> Chances are, you have a problem with your
>
> On 5/30/07, ousseynou diagne <..hidden..> wrote:
>>
>> I  am migrating our Sql-Ledger 2.6.15 with Postgres 8.2.0  to Ledger-Smb
>> 1.1.12  I have follow all the steps outlined on the the Wiki HOWTO
>> Update an existing SQL-Ledger installation to run with LedgerSMB.  After
>> accessing the new system to logon the page  will  display  Upgrading to
>> Version 1.1.12 … message , stay busy for a while and  seems to finish by
>> shown done at the bottom left of the web page. If try to reconnect again
>> the system shows login disabled!.  If I connect to the admin interface
>> and unlock, I got the same message again when I logon to the system
>> (Upgrading to Version 1.1.12) … and so on…
>> Anyone has an idea what may be wrong.   When I connect to the admin
>> interface, all my users have been migrated but from the Pg Database
>> Administration interface the database user is now ledger-smb (which I
>> guess is ok since I have migrated). The problem, (if it is?) is that
>> Sql-ledger user is still the owner of the database and tables. I thought
>> this was the problem and have added the ledger-smb user with the
>> Superuser, Creatdb Createrole, Login roles  and Password  but it did not
>> help.   I  also tried changing the database user ledger-smb to
>> sql-ledger by editing the file /usr/local/ledger-smb/bin/admin.pl to
>> replace ledger-smb by sql-ledger since sql-ledger is still the owner of
>> the database. It did not workout.    I need help please     I am running
>> this on our test database which is a duplicate of our production system.
>> We have done some customizations on our system but I don't think it is
>> the problem.
>>
>>
>> Any help would be appreciated
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Ledger-smb-users mailing list
>> ..hidden..
>> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Ledger-smb-users mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Ledger-smb-users mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users