← Back to team overview

dhis2-devs team mailing list archive

Re: Upgrading to 2.24 and /api/24/metadata issue

 

We can try that.

Regards
Vanya

On Tue, Aug 23, 2016 at 2:34 PM, Morten Olav Hansen <morten@xxxxxxxxx>
wrote:

> Maybe you should turn of PG logging the DDL statements.. maybe there is
> startdate failed because of xyz, could be useful in hunting down the issue..
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Tue, Aug 23, 2016 at 3:55 PM, Vanya Seth <vanyas@xxxxxxxxxxxxxxxx>
> wrote:
>
>> Well its very strange as this works fine in our local machines.
>>
>> On the VM's even tried dropping the db, creating new and then deploying
>> the war. Still to no avail.
>>
>> Mostly this manual creation of columns should work. But what if there are
>> other such things that might have been missed and will only come up when we
>> try to do some operations.
>>
>> Regards
>> Vanya
>>
>> On Tue, Aug 23, 2016 at 1:06 PM, Morten Olav Hansen <morten@xxxxxxxxx>
>> wrote:
>>
>>> That sounds strange Vanya, looked at the HBM files and there was nothing
>>> special about those fields.
>>>
>>> Could you try a manual add:
>>> alter table mapview add column startdate timestamp without time zone
>>> alter table mapview add column enddate timestamp without time zone
>>>
>>> and see if that fixes it (I haven't seen this issue anywhere else, so
>>> could be something very local)
>>>
>>> --
>>> Morten Olav Hansen
>>> Senior Engineer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Tue, Aug 23, 2016 at 1:59 PM, Vanya Seth <vanyas@xxxxxxxxxxxxxxxx>
>>> wrote:
>>>
>>>>
>>>> Hello devs
>>>>
>>>> We were updating our test VM's to 2.24 from 2.21. We did it in an
>>>> incremental manner.
>>>> Apparently on few of the VM's after upgrade the /api/24/metadata (GET)
>>>> call is failing with the following error:
>>>>
>>>> WARN  2016-08-23 11:47:59,957 SQL Error: 0, SQLState: 42703
>>>> (SqlExceptionHelper.java [http-bio-8080-exec-8])
>>>> * ERROR 2016-08-23 11:47:59,957 ERROR: column this_.startdate does not
>>>> exist
>>>>   Position: 463 (SqlExceptionHelper.java [http-bio-8080-exec-8])
>>>> org.hibernate.exception.SQLGrammarException: could not extract
>>>> ResultSet
>>>>
>>>> We checked the startup logs and there was no specific error around
>>>> table update errors. It seems the mapview relation now has two new columns
>>>> 'startdate' and 'enddate'. These are not getting created during the
>>>> deployment and hence the metadata export call is failing.
>>>>
>>>> Tried stopping the server and restarting it multiple times but to no
>>>> avail.
>>>>
>>>> Can you please look into this and let know what could be causing this
>>>> strange issue.
>>>>
>>>> --
>>>> With Regards
>>>> Vanya
>>>>
>>>> ThoughtWorks Technologies
>>>> Hyderabad
>>>>
>>>> --Stay Hungry Stay Foolish!!
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>>
>> --
>> With Regards
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!

References