error after run analystic

Channara · 5 October 2015 09:14

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

···

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Alex_Tumwesigye · 5 October 2015 09:20

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

···

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Channara · 5 October 2015 09:33

so you mean, i can delete row from table? which table should i can delete that row?

···

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Alex_Tumwesigye · 5 October 2015 09:34

period table but make sure you delete only that row.

Alex

···

On Mon, Oct 5, 2015 at 12:33 PM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

–

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Knut_Staring · 5 October 2015 09:36

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

···

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

Knut_Staring · 5 October 2015 09:37

Oops, wrong order. Should be like this, I think:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period GROUP BY startdate, enddate HAVING count(*) >1)

···

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

–

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

Knut_Staring · 5 October 2015 09:39

Still some typos…

SELECT * FROM period WHERE (startdate, enddate) IN

(SELECT startdate, enddate FROM period GROUP BY startdate, enddate HAVING count(*) >1)

···

On Mon, Oct 5, 2015 at 11:37 AM, Knut Staring knutst@gmail.com wrote:

Oops, wrong order. Should be like this, I think:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period GROUP BY startdate, enddate HAVING count(*) >1)

–

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

–
Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

jason · 5 October 2015 09:41

And you may want to be careful about deleting anything as there may be data attached to one of those periods. You should of course make a backup before you attempt to delete anything, and then find any data which is referencing the duplicate period. There are quite a few tables which reference “period”, so you may need to check these.

However, if you get back a period which does not actually correspond to the correct period type (for instance, a year with a period type as a week), that is the one you should focus on trying to get rid of.

Regards

Jason

···

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Channara · 5 October 2015 10:02

thank you jason
by the way, i run already. but didn’t see any record show up

···

On Mon, Oct 5, 2015 at 4:41 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

And you may want to be careful about deleting anything as there may be data attached to one of those periods. You should of course make a backup before you attempt to delete anything, and then find any data which is referencing the duplicate period. There are quite a few tables which reference “period”, so you may need to check these.

However, if you get back a period which does not actually correspond to the correct period type (for instance, a year with a period type as a week), that is the one you should focus on trying to get rid of.

Regards

Jason

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

–

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

jason · 5 October 2015 10:24

What time zone are you on and which version are you using?

···

On Mon, Oct 5, 2015 at 12:02 PM, channara rin rin.channara@gmail.com wrote:

thank you jason
by the way, i run already. but didn’t see any record show up

–

On Mon, Oct 5, 2015 at 4:41 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

And you may want to be careful about deleting anything as there may be data attached to one of those periods. You should of course make a backup before you attempt to delete anything, and then find any data which is referencing the duplicate period. There are quite a few tables which reference “period”, so you may need to check these.

However, if you get back a period which does not actually correspond to the correct period type (for instance, a year with a period type as a week), that is the one you should focus on trying to get rid of.

Regards

Jason

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

–

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Channara · 5 October 2015 10:30

Hi Jason,
I am using version 2.20 and Time zone: GMT+7:00

···

On Mon, Oct 5, 2015 at 5:24 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

What time zone are you on and which version are you using?

On Mon, Oct 5, 2015 at 12:02 PM, channara rin rin.channara@gmail.com wrote:

thank you jason
by the way, i run already. but didn’t see any record show up

–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On Mon, Oct 5, 2015 at 4:41 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

And you may want to be careful about deleting anything as there may be data attached to one of those periods. You should of course make a backup before you attempt to delete anything, and then find any data which is referencing the duplicate period. There are quite a few tables which reference “period”, so you may need to check these.

However, if you get back a period which does not actually correspond to the correct period type (for instance, a year with a period type as a week), that is the one you should focus on trying to get rid of.

Regards

Jason

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

–

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

jason · 5 October 2015 11:21

What about

SELECT * FROM period where startdate = ‘1975-01-01’::date

···

On Mon, Oct 5, 2015 at 12:30 PM, channara rin rin.channara@gmail.com wrote:

Hi Jason,
I am using version 2.20 and Time zone: GMT+7:00

–

On Mon, Oct 5, 2015 at 5:24 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

What time zone are you on and which version are you using?

On Mon, Oct 5, 2015 at 12:02 PM, channara rin rin.channara@gmail.com wrote:

thank you jason
by the way, i run already. but didn’t see any record show up

–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On Mon, Oct 5, 2015 at 4:41 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

And you may want to be careful about deleting anything as there may be data attached to one of those periods. You should of course make a backup before you attempt to delete anything, and then find any data which is referencing the duplicate period. There are quite a few tables which reference “period”, so you may need to check these.

However, if you get back a period which does not actually correspond to the correct period type (for instance, a year with a period type as a week), that is the one you should focus on trying to get rid of.

Regards

Jason

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

–

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

Channara · 5 October 2015 11:36

No record found…

···

On Mon, Oct 5, 2015 at 6:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

What about

SELECT * FROM period where startdate = ‘1975-01-01’::date

On Mon, Oct 5, 2015 at 12:30 PM, channara rin rin.channara@gmail.com wrote:

Hi Jason,
I am using version 2.20 and Time zone: GMT+7:00

–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On Mon, Oct 5, 2015 at 5:24 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

What time zone are you on and which version are you using?

On Mon, Oct 5, 2015 at 12:02 PM, channara rin rin.channara@gmail.com wrote:

thank you jason
by the way, i run already. but didn’t see any record show up

–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On Mon, Oct 5, 2015 at 4:41 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

And you may want to be careful about deleting anything as there may be data attached to one of those periods. You should of course make a backup before you attempt to delete anything, and then find any data which is referencing the duplicate period. There are quite a few tables which reference “period”, so you may need to check these.

However, if you get back a period which does not actually correspond to the correct period type (for instance, a year with a period type as a week), that is the one you should focus on trying to get rid of.

Regards

Jason

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

–

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "

Channara · 5 October 2015 11:37

RUN

···

On Mon, Oct 5, 2015 at 6:36 PM, channara rin rin.channara@gmail.com wrote:

No record found…

On Mon, Oct 5, 2015 at 6:21 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

What about

SELECT * FROM period where startdate = ‘1975-01-01’::date

On Mon, Oct 5, 2015 at 12:30 PM, channara rin rin.channara@gmail.com wrote:

Hi Jason,
I am using version 2.20 and Time zone: GMT+7:00

–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On Mon, Oct 5, 2015 at 5:24 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

What time zone are you on and which version are you using?

On Mon, Oct 5, 2015 at 12:02 PM, channara rin rin.channara@gmail.com wrote:

thank you jason
by the way, i run already. but didn’t see any record show up

–
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

On Mon, Oct 5, 2015 at 4:41 PM, Jason Pickering jason.p.pickering@gmail.com wrote:

And you may want to be careful about deleting anything as there may be data attached to one of those periods. You should of course make a backup before you attempt to delete anything, and then find any data which is referencing the duplicate period. There are quite a few tables which reference “period”, so you may need to check these.

However, if you get back a period which does not actually correspond to the correct period type (for instance, a year with a period type as a week), that is the one you should focus on trying to get rid of.

Regards

Jason

On Mon, Oct 5, 2015 at 11:36 AM, Knut Staring knutst@gmail.com wrote:

The table is called period.

But please first run this query:

SELECT * FROM period WHERE startdata, enddate IN

(SELECT startdate, endedate FROM period HAVING count(*) >1 GROUP BY startdate, enddate)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049

–

On Mon, Oct 5, 2015 at 11:33 AM, channara rin rin.channara@gmail.com wrote:

so you mean, i can delete row from table? which table should i can delete that row?

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–

Knut Staring

Dept. of Informatics, University of Oslo

Norway: +4791880522

Skype: knutstar

http://dhis2.org

On Mon, Oct 5, 2015 at 4:20 PM, Alex Tumwesigye atumwesigye@gmail.com wrote:

Dear Channara,

Which version are you running? This bug was fixed. It is related to timezone I f I remember very well.

If you check your period table, there are invalid ranges for 1975-01-01. Just delete the invalid ranges and you will be fine.

Alex

On Mon, Oct 5, 2015 at 12:14 PM, channara rin rin.channara@gmail.com wrote:

Hi DHIS2 member,
i got the message from DHIS2 system like below. can you help me how to fix this problem?

=====================================================

Resource table process failed, please check the logs. Time: 2015-10-05T00:00:08.388+07:00. Message: PreparedStatementCallback; SQL [insert into _dateperiodstructure values (?,?,?,?,?,?,?,?,?,?,?,?)]; ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.; nested exception is org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint “_dateperiodstructure_pkey”

Detail: Key (dateperiod)=(1975-01-01) already exists.

at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2198)

at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1927)

at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1130)

at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:396)

at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2892)

at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:1005)

at org.springframework.jdbc.core.JdbcTemplate$4.doInPreparedStatement(JdbcTemplate.java:989)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644)

at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:673)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:989)

at org.springframework.jdbc.core.BatchUpdateUtils.executeBatchUpdate(BatchUpdateUtils.java:32)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1039)

at org.springframework.jdbc.core.JdbcTemplate.batchUpdate(JdbcTemplate.java:1034)

at org.hisp.dhis.resourcetable.jdbc.JdbcResourceTableStore.batchUpdate(JdbcResourceTableStore.java:101)

at org.hisp.dhis.resourcetable.DefaultResourceTableService.generateDatePeriodTable(DefaultResourceTableService.java:456)

at sun.reflect.GeneratedMethodAccessor2260.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201)

at com.sun.proxy.$Proxy104.generateDatePeriodTable(Unknown Source)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.generateAll(ResourceTableTask.java:121)

at org.hisp.dhis.resourcetable.scheduling.ResourceTableTask.run(ResourceTableTask.java:85)

at org.hisp.dhis.scheduling.ScheduledTasks.run(ScheduledTasks.java:60)

at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)

at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET

Kampala

Uganda

IT Consultant - BarefootPower Uganda Ltd, SmartSolar, Kenya

IT Specialist (Servers, Networks and Security, Health Information Systems - DHIS2 ) & Solar Consultant

+256 774149 775, + 256 759 800161

"I don’t want to be anything other than what I have been - one tree hill "