Great question.

Deploying the latest WAR file should automatically upgrade your DB to
the correct version.  Since we are still in development stages for v1.1,
there are sometimes DB upgrade errors in this process, in which case you
should open an issue in the issue tracker (and perhaps send email the
list also, so that others are aware of the issue ).  We will ensure that
upgrades are thoroughly tested as part of our v1.1 QA prior to the
official release so that these issues do not occur in production.

Thanks,

Aliya

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Joey
Tuvilla
Sent: Friday, November 02, 2007 12:16 PM
To: Developer
Subject: Re: [Mifos-developer] Mifos Database Upgrade error

 

Hello All,

 

Question regarding DB upgrade:

 

For instance you already have a DB (153) running with data, what is the
process in upgrading DB 153  to 154 ? Will the latest WAR file
automatically  upgrade the DB when deployed? 

 

Please advice steps in this scenario.

 

Thanks,

 

Joey

________________________________

From: [EMAIL PROTECTED]
[EMAIL PROTECTED] On Behalf Of Van
Mittal-Henkle [EMAIL PROTECTED]
Sent: Friday, November 02, 2007 7:00 AM
To: Developer
Subject: Re: [Mifos-developer] Mifos Database Upgrade error

Hi Gary,

 

It looks like you're haviing some trouble with a mismatch between the
WAR file you're using and the source code you have checked out.

 

Running the ant build target "build_db" will create a clean new version
of the database for you to use.  The database version will correspond to
what is in the revision of the source code you have checked out.  The
database version and application version have been at 154 since revision
12167 which was committed on October 23rd.  This means that you are
using a WAR file built before revision 12167 but that the current source
code you have checked out is at or after revision 12167.

 

I would recommend that you go through the following steps:

 

1) do an svn update to get the latest revision of mifos

2) build a new WAR file using the latest revision

3) remove the current war file you are using and replace it with the new
WAR file

4) run the ant build target "build_db" to start from a clean DB that is
at the same version as the WAR file

5) restart your app server and you should be up and running

 

Let us know if this works for you.

 

Cheers,

--Van

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gary
Weberg
Sent: Tuesday, October 30, 2007 10:40 AM
To: 'Developer'
Subject: [Mifos-developer] Mifos Database Upgrade error

Hello,

 

We are getting a Mifos Database upgrade error. See attached doc file.
The error indicated that our Application DB version is 153, yet the
Database version is 154.  I found the SQL scripts to downgrade the DB
from 154 153.  When I run the SQL scripts I get the errors:

 

Line 1:  Error on rename of '.\mifos\#sql-620_2' to
'.\mifos\loan_Account' (errno: 150)

Line 2:  Duplicate column name 'PARENT'_ACCOUNT_ID'

 

The script is:

 

ALTER TABLE LOAN_ACCOUNT DROP COLUMN PARENT_ACCOUNT_ID;

ALTER TABLE LOAN_ACCOUNT ADD COLUMN  PARENT_ACCOUNT_ID INTEGER;

 

ALTER TABLE LOAN_ACCOUNT ADD FOREIGN KEY (PARENT_ACCOUNT_ID)

  REFERENCES  ACCOUNT(ACCOUNT_ID) ON DELETE NO ACTION  ON UPDATE NO
ACTION;

  

 

UPDATE DATABASE_VERSION SET DATABASE_VERSION = 153 WHERE
DATABASE_VERSION = 154;

 

Does anyone know what is causing the SQL errors?

 

I removed all the lines except the last and at least I can get the DB
version changed.  This allows us to access Mifos again, but without
altering the tables.

 

Also, I suppose by running the ANT target build_db that I upgraded the
DB to 154, but the AP was still at 153.  Is this normal to upgrade the
DB schema prior to upgrading the DB?  This was been an issue for more
than a week now.  We waited a week hoping the AP would be brought up to
version 154.

 

Thanks for the help,

 

Gary

 

 

 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

Reply via email to