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.
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.
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@dhis2.org 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)
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.
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.
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.
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@dhis2.org 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)
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.