sql-ledger-users

[SL] Problems upgrading from 2.6.27 to 2.8.0

[Glen M. <gl...@au...>]

When I upgraded from 2.6.27 to 2.8.0 I couldn't login.

I unlocked the system from the admin interface but when I try to login I 
get:

    Upgrading to Version 2.8.0 ...


        Error!

    *create sequence assemblyid*
    *ERROR: relation "assemblyid" already exists*

*
*Also according to the upgrade docs there should be the following files 
in the templates directory but they aren't there:

    3. copy the following templates from the templates directory to
       your private directory

       Default-credit_invoice.html
       Default-credit_invoice.tex
       Default-debit_invoice.html
       Default-debit_invoice.tex

Regards, Glen
**

-- 
Glen Morris: Arachnoid Australia
613 90175780 Melbourne | 612 90164032 Sydney
613 98961811 VoIP | Mbl 0419299140
Skype=glenmo. PO Box 214, Healesville VIC 3777, Australia

Re: [SL] Problems upgrading from 2.6.27 to 2.8.0

[Dieter S. <dsi...@sq...>]

The easiest is to restore from a backup, delete the second record in the 
defaults table and upgrade again.

If you don't have a backup you have no choice but to do a manual upgrade 
from the point on when the upgrade script failed. The upgrade failed in 
Pg-upgrade-2.7.5-2.7.6.sql when it tried to rewrite the defaults table.

-- 
Dieter Simader       http://www.sql-ledger.com   Tel: (780) 472-8161
DWS Systems Inc.        Accounting Software      Fax: (780) 478-5281
============== On a clear disk you can seek forever ================

On Mon, 2 Apr 2007, Glen Morris wrote:

> When I upgraded from 2.6.27 to 2.8.0 I couldn't login.
>
> I unlocked the system from the admin interface but when I try to login I
> get:
>
>    Upgrading to Version 2.8.0 ...
>
>
>        Error!
>
>    *create sequence assemblyid*
>    *ERROR: relation "assemblyid" already exists*
>
> *
> *Also according to the upgrade docs there should be the following files
> in the templates directory but they aren't there:
>
>    3. copy the following templates from the templates directory to
>       your private directory
>
>       Default-credit_invoice.html
>       Default-credit_invoice.tex
>       Default-debit_invoice.html
>       Default-debit_invoice.tex
>
> Regards, Glen
> **
>
>

Re: [SL] Problems upgrading from 2.6.27 to 2.8.0

[ATM L. <atm...@km...>]

I am back at 2.6.14 and was just about to go to the 2.7 (support) version...
Should I jump to 2.8 instead?  After a backup, should I be worried about the
update?  
 
> The easiest is to restore from a backup, delete the second 
> record in the defaults table and upgrade again.
> 

Re: [SL] Problems upgrading from 2.6.27 to 2.8.0

[Tage D. <ta...@ht...>]

Dieter Simader wrote:
> The easiest is to restore from a backup, delete the second record in the 
> defaults table and upgrade again.
>
> If you don't have a backup you have no choice but to do a manual upgrade 
> from the point on when the upgrade script failed. The upgrade failed in 
> Pg-upgrade-2.7.5-2.7.6.sql when it tried to rewrite the defaults table.
>
>   
Sorry it don't work, and come with this error

Upgrading to Version 2.8.0 ...
Error!

create table cargo (id int not null, trans_id int not null, package 
text, netweight float4, grossweight float4, volume float4)
ERROR: could not create relation 1663/17233/111289: Filen eksisterer 
{file exist}

hope it will be better

Tage from Denmark

Re: [SL] Problems upgrading from 2.6.27 to 2.8.0

[George O. <geo...@ya...>]

On Tuesday 03 April 2007 03:56, Tage Danielsen wrote:
> Dieter Simader wrote:
> > The easiest is to restore from a backup, delete the second record in the
> > defaults table and upgrade again.
> >
> > If you don't have a backup you have no choice but to do a manual upgrade
> > from the point on when the upgrade script failed. The upgrade failed in
> > Pg-upgrade-2.7.5-2.7.6.sql when it tried to rewrite the defaults table.
>
> Sorry it don't work, and come with this error

I have done this once before for earlier version. If you do not have backup or 
at least system backup to get back to previous version you will have to go 
manually and delete all existing files, tables and edit the sql file error by 
error. Every time you do something run the setup it will give you another 
error. Then you will have to back track and repeat all the steps you have 
made to that point and so on. It is painfull but it will teach you one thing:
Always have a backup before any upgrade.


> Upgrading to Version 2.8.0 ...
> Error!
>
> create table cargo (id int not null, trans_id int not null, package
> text, netweight float4, grossweight float4, volume float4)
> ERROR: could not create relation 1663/17233/111289: Filen eksisterer
> {file exist}
>
> hope it will be better
>
> Tage from Denmark
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users

-- 
George
AUSTRALIA
http://www.okstudio.com.au

Re: [SL] Problems upgrading from 2.6.27 to 2.8.0

[Tage D. <ta...@ht...>]

George Osvald wrote:
> On Tuesday 03 April 2007 03:56, Tage Danielsen wrote:
>   
>> Dieter Simader wrote:
>>     
>>> The easiest is to restore from a backup, delete the second record in the
>>> defaults table and upgrade again.
>>>
>>> If you don't have a backup you have no choice but to do a manual upgrade
>>> from the point on when the upgrade script failed. The upgrade failed in
>>> Pg-upgrade-2.7.5-2.7.6.sql when it tried to rewrite the defaults table.
>>>       
>> Sorry it don't work, and come with this error
>>     
>
> I have done this once before for earlier version. If you do not have backup or 
> at least system backup to get back to previous version you will have to go 
> manually and delete all existing files, tables and edit the sql file error by 
> error. Every time you do something run the setup it will give you another 
> error. Then you will have to back track and repeat all the steps you have 
> made to that point and so on. It is painfull but it will teach you one thing:
> Always have a backup before any upgrade.
>
>
>   
>> Upgrading to Version 2.8.0 ...
>> Error!
>>
>> create table cargo (id int not null, trans_id int not null, package
>> text, netweight float4, grossweight float4, volume float4)
>> ERROR: could not create relation 1663/17233/111289: Filen eksisterer
>> {file exist}
>>
>> hope it will be better
>>
>> Tage from Denmark
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your opinions on IT & business topics through brief surveys-and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>     
>
>   
The problem is not backup, I made at filebackup of database and 
sql-ledger, and I am running 2.6.27 very OK, but I like to upgrade to 
2.8 due to new features, and this is not running.

Tage from Denmark