Analytics error after upgrade to 2.29

Support - Assistance technique
1

There seems to be a problem with year (it is trying to insert 2015 in a table that requires 2014). Does anyone have an insight into why this happens?

Caused by: org.postgresql.util.PSQLException: ERROR: new row for relation “analytics_completeness_temp_2014” violates check constraint “analytics_completeness_temp_2014_yearly_check”

Detail: Failing row contains (null, null, null, null, XbBIPEpxTue, XbBIPEpxTue, aRxa6o8GqZN, HfVjCurKxh2, t0J75eHKxz5, xLWuQq3DjOR, iZNVvlnVxm6, ELzS3pnwJyh, null, null, null, null, null, null, null, 2015W1, null, null, null, null, 2015BiW0, 201501, 201501B, 2015Q1, 2015S1, 2014AprilS2, 2015, 2014April, 2014July, 2014Oct, t, zJrL4HQqYmD, 2015-01-06).

2

Still not sure why this error arose, but *fixed it" by deleting completenessregistrations from before 2015:

delete from completedatasetregistration where periodid in (select periodid from period where startdate <‘2015-01-01’)

···

On Tue, May 8, 2018 at 7:43 PM, Knut Staring knutst@gmail.com wrote:

There seems to be a problem with year (it is trying to insert 2015 in a table that requires 2014). Does anyone have an insight into why this happens?

Caused by: org.postgresql.util.PSQLException: ERROR: new row for relation “analytics_completeness_temp_2014” violates check constraint “analytics_completeness_temp_2014_yearly_check”

Detail: Failing row contains (null, null, null, null, XbBIPEpxTue, XbBIPEpxTue, aRxa6o8GqZN, HfVjCurKxh2, t0J75eHKxz5, xLWuQq3DjOR, iZNVvlnVxm6, ELzS3pnwJyh, null, null, null, null, null, null, null, 2015W1, null, null, null, null, 2015BiW0, 201501, 201501B, 2015Q1, 2015S1, 2014AprilS2, 2015, 2014April, 2014July, 2014Oct, t, zJrL4HQqYmD, 2015-01-06).

–

Knut Staring

Department of Information, Evidence and Research
World Health Organization, Geneva, Switzerland
Office: +41 22 791 3683 Mob1: +33 6 4434 2931 Mob2: +47 9188 0522
Skype: knutstar