| Thread Previous • Date Previous • Date Next • Thread Next |
Hi Bob and Developers, I have had the same error some days ago. We recently made the upgrade from 2.26 to 2.29 (Build revision: 9c273a5) . The upgrade was made by the BAO Team. The problem appears not immediatly after the upgrade, but when I tried to correct a wrong event date. One of the OrgUnits, inserted a date in the year 2015 instead of 2016. The wrong event was the only one event in 2015. I have temporary resolved the problem restoring the old wrong date of the event and excluding the 2015 year from the event report statistics, but the problem remain. Please, let me know when the problem would be solved, in order to upgrade our instance and make the corrections of the wrong date. Regards, Antonia This is the initial part of the message. I attache the entire message received. --------------------------------------- KRG Health Monitoring System Message [No reply] <dev@xxxxxxxxxxx> 24 luglio 2018 19:53 Job 'inMemoryAnalyticsJob' failed System title: KRG Health Monitoring System Base URL: https://krg-dhis.ipro-it.eu Time: 2018-07-24T13:53:22.026-04:00 Message: StatementCallback; uncategorized SQLException for SQL [drop table analytics_event_g9utevaaxdk]; SQL state [2BP01]; error code [0]; ERROR: cannot drop table analytics_event_g9utevaaxdk because other objects depend on it Detail: table analytics_event_2015_g9utevaaxdk depends on table analytics_event_g9utevaaxdk Hint: Use DROP ... CASCADE to drop the dependent objects too.; nested exception is org.postgresql.util. PSQLException: ERROR: cannot drop table analytics_event_g9utevaaxdk because other objects depend on it Detail: table analytics_event_2015_g9utevaaxdk depends on table analytics_event_g9utevaaxdk Hint: Use DROP ... CASCADE to drop the dependent objects too. -- Eng. Antonia Bezenchek CIO - ICT Network & Security Engineer <http://www.ipro-it.eu/> InformaPRO S.r.l. via G. Guinizelli 98/100, Rome 00152, Italy <https://www.google.com/maps/place/InformaPRO+S.r.l./@41.8740594,12.4592301,17z/data=!4m12!1m6!3m5!1s0x132f6029b8bd3673:0xf31e9a39e5b5ac35!2sInformaPRO+S.r.l.!8m2!3d41.8740352!4d12.4591429!3m4!1s0x132f6029b8bd3673:0xf31e9a39e5b5ac35!8m2!3d41.8740352!4d12.4591429>, VAT: IT08095781004 Tel. +39 06 5502218 / +39 06 5882352 Fax +39 06 62207168 Mobile: +39 3938733585 Skype: informa_antonia.bezenchek www.ipro-it.eu --> *Follow us on *LinkedIn <https://www.linkedin.com/company/informapro/> On Wed, Aug 1, 2018 at 2:20 PM Bob Jolliffe <bobjolliffe@xxxxxxxxx> wrote: > Hi Adolphe > > By strange coincidence Lamin (from the Gambia) was seeing the same error > yesterday. Though the sequence is reversed from what David has described. > The nightly scheduled run was completing successfully but the manual run > was failing with this error about dependent analytics tables. > > @Lamin you did something regarding period selection and then it seemed to > work. Can you explain to the list? > > Regards > Bob > > On 31 July 2018 at 17:55, Kamugunga Adolphe <kaadol@xxxxxxxxx> wrote: > >> Dear Dave, >> >> I tried your workaround but analytics run once successfully and compile >> aggregate values of my weekly reports only, the dashboard with cases based >> data(program indicators) don't have values. The strange situation is that >> from Event Reports app, i list/display events reported before upgrade only >> and when i change the period to "This month" no values displayed. >> >> I run again the analytics but it failed with similar message. If someone >> has another alternative to fix this plz let me know! I am completely stack? >> The instance is updated with the today build version Version:2.29Build >> revision:153207cBuild date:2018-07-31 06:50Jasper reports version:6.3.1 >> >> >> Down here is the error message content: >> >> >> >> >> Job 'inMemoryAnalyticsJob' failed >> >> System title:Integrated Disease Surveillance >> Base URL: >> Time: 2018-07-31T16:04:01.496+02:00 >> Message: StatementCallback; uncategorized SQLException for SQL [drop >> table analytics]; SQL state [2BP01]; error code [0]; ERROR: cannot drop >> table analytics because other objects depend on it >> Detail: table analytics_2004 depends on table analytics >> table analytics_2005 depends on table analytics >> table analytics_2007 depends on table analytics >> table analytics_2008 depends on table analytics >> table analytics_2009 depends on table analytics >> table analytics_2010 depends on table analytics >> table analytics_2011 depends on table analytics >> table analytics_2012 depends on table analytics >> table analytics_2013 depends on table analytics >> table analytics_2014 depends on table analytics >> table analytics_2015 depends on table analytics >> Hint: Use DROP ... CASCADE to drop the dependent objects too.; nested >> exception is org.postgresql.util.PSQLException: ERROR: cannot drop table >> analytics because other objects depend on it >> Detail: table analytics_2004 depends on table analytics >> table analytics_2005 depends on table analytics >> table analytics_2007 depends on table analytics >> table analytics_2008 depends on table analytics >> table analytics_2009 depends on table analytics >> table analytics_2010 depends on table analytics >> table analytics_2011 depends on table analytics >> table analytics_2012 depends on table analytics >> table analytics_2013 depends on table analytics >> table analytics_2014 depends on table analytics >> table analytics_2015 depends on table analytics >> Hint: Use DROP ... CASCADE to drop the dependent objects too. >> >> Cause: org.postgresql.util.PSQLException: ERROR: cannot drop table >> analytics because other objects depend on it >> Detail: table analytics_2004 depends on table analytics >> table analytics_2005 depends on table analytics >> table analytics_2007 depends on table analytics >> table analytics_2008 depends on table analytics >> table analytics_2009 depends on table analytics >> table analytics_2010 depends on table analytics >> table analytics_2011 depends on table analytics >> table analytics_2012 depends on table analytics >> table analytics_2013 depends on table analytics >> table analytics_2014 depends on table analytics >> table analytics_2015 depends on table analytics >> Hint: Use DROP ... CASCADE to drop the dependent objects too. >> at >> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2422) >> at >> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2167) >> at >> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:306) >> at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441) >> at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365) >> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307) >> at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:293) >> at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:270) >> at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:266) >> at >> com.mchange.v2.c3p0.impl.NewProxyStatement.execute(NewProxyStatement.java:75) >> at >> org.springframework.jdbc.core.JdbcTemplate$1ExecuteStatementCallback.doInStatement(JdbcTemplate.java:436) >> at >> org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:408) >> at >> org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:445) >> at >> org.hisp.dhis.analytics.table.AbstractJdbcTableManager.executeSilently(AbstractJdbcTableManager.java:341) >> at >> org.hisp.dhis.analytics.table.AbstractJdbcTableManager.swapTable(AbstractJdbcTableManager.java:508) >> at >> org.hisp.dhis.analytics.table.AbstractJdbcTableManager.swapTable(AbstractJdbcTableManager.java:178) >> at sun.reflect.GeneratedMethodAccessor2130.invoke(Unknown Source) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:498) >> at >> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) >> at >> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) >> at com.sun.proxy.$Proxy142.swapTable(Unknown Source) >> at >> org.hisp.dhis.analytics.table.DefaultAnalyticsTableService.lambda$swapTables$5(DefaultAnalyticsTableService.java:373) >> at java.util.ArrayList.forEach(ArrayList.java:1249) >> at >> org.hisp.dhis.analytics.table.DefaultAnalyticsTableService.swapTables(DefaultAnalyticsTableService.java:373) >> at >> org.hisp.dhis.analytics.table.DefaultAnalyticsTableService.update(DefaultAnalyticsTableService.java:171) >> at >> org.hisp.dhis.analytics.table.DefaultAnalyticsTableGenerator.generateTables(DefaultAnalyticsTableGenerator.java:115) >> at >> org.hisp.dhis.analytics.table.scheduling.AnalyticsTableJob.execute(AnalyticsTableJob.java:70) >> at >> org.hisp.dhis.scheduling.DefaultJobInstance.executeJob(DefaultJobInstance.java:145) >> at >> org.hisp.dhis.scheduling.DefaultJobInstance.execute(DefaultJobInstance.java:59) >> at >> org.hisp.dhis.scheduling.DefaultSchedulingManager.lambda$internalExecuteJobConfiguration$2(DefaultSchedulingManager.java:237) >> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at >> org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) >> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> at java.lang.Thread.run(Thread.java:745) >> >> >> >> *Adolphe Kamugunga* >> *MIS Technical Advisor* >> Mobile: +250 788 740 578 >> Email:kaadol@xxxxxxxxx >> Skype: ka.adolphe >> RWANDA >> >> >> On 5 July 2018 at 15:38, David Huser <dhuser@xxxxxxxxxxxxxx> wrote: >> >>> Is it possible that the Reports app to run analytics does something >>> different to what the Scheduler does, not dropping / creating the same >>> tables? We added a JIRA issue <https://jira.dhis2.org/browse/DHIS2-4214> >>> describing this - Scheduler cannot complete analytics generation once >>> Reports has created analytics beforehand. >>> >>> A workaround for now is so far is to clear analytics via Data Admin > >>> Maintenance then using the Scheduler only to run - manually or scheduled. >>> >>> Regards, >>> David >>> >>> On Wed, Jul 4, 2018 at 6:28 PM gerald thomas <gerald17006@xxxxxxxxx> >>> wrote: >>> >>>> Dear Jason, >>>> That is true but the errors are still generating into the various >>>> analytics tables. That is why I wanted him to check those tables and if >>>> there are data in them he should delete them. >>>> >>>> On Wed, 4 Jul 2018 at 15:53, Jason Pickering < >>>> jason.p.pickering@xxxxxxxxx> wrote: >>>> >>>>> Hi Adolphe, >>>>> >>>>> The error points to lack of disk space. Check that as well. >>>>> >>>>> Regards, >>>>> Jason >>>>> >>>>> On Wed, Jul 4, 2018, 10:55 gerald thomas <gerald17006@xxxxxxxxx> >>>>> wrote: >>>>> >>>>>> Dear Kamugunga, >>>>>> I think they are still in the completedatasetregistration. Please run >>>>>> the query below so that we can know the quantity. >>>>>> We will have to delete them here and at the analytics tables again. >>>>>> >>>>>> dhis-# SELECT p.startdate, count(dv.datasetid) as recno from >>>>>> completedatasetregistration dv INNER JOIN period p on >>>>>> p.periodid=dv.periodid group by p.startdate order by p.startdate; >>>>>> >>>>>> >>>>>> On Wed, 4 Jul 2018 at 14:43, Kamugunga Adolphe <kaadol@xxxxxxxxx> >>>>>> wrote: >>>>>> >>>>>>> Hi Thomas and Dan for sharing your experience, >>>>>>> However i have dropped the analytics table and analytics_temp >>>>>>> tables. and deploy my the recent war file. Then i run the analytics >>>>>>> successfully. Afterward i started receiven the same massage as by >>>>>>> attachment. >>>>>>> >>>>>>> I am suspecting jobs that are by default created in the new feature >>>>>>> of "Scheduler" Can any one explain reasons of having these? And please >>>>>>> share more hints on how to deal with this problem. >>>>>>> >>>>>>> Regards >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Adolphe Kamugunga* >>>>>>> *MIS Technical Advisor* >>>>>>> Mobile: +250 788 740 578 >>>>>>> Email:kaadol@xxxxxxxxx >>>>>>> Skype: ka.adolphe >>>>>>> RWANDA >>>>>>> >>>>>>> >>>>>>> On 3 July 2018 at 23:56, gerald thomas <gerald17006@xxxxxxxxx> >>>>>>> wrote: >>>>>>> >>>>>>>> Dear Kamugunga, >>>>>>>> I think you need to shutdown instance; remove your current war file >>>>>>>> folder e.g ROOT or dhis which depends on the name of your war file. >>>>>>>> Switch to your Postgres database and manually delete all those >>>>>>>> analytics tables. Then you restart instance and monitor log at startup and >>>>>>>> when running analytics again. >>>>>>>> >>>>>>>> >>>>>>>> On Tue, 3 Jul 2018 at 16:57, Kamugunga Adolphe <kaadol@xxxxxxxxx> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I have upgraded my 2.28 instance to 2.29 version,7c81fba >>>>>>>>> Build date: 2018-06-28 06:46 . I have run the upgrade scripts >>>>>>>>> before as instructed in guide. My server runs ubuntu 14.04 and postgresql >>>>>>>>> 9.5.5. >>>>>>>>> >>>>>>>>> However since then, my analytics is not running, i am receiving >>>>>>>>> number of system emails with subject " Job 'Credentials expiry alert' >>>>>>>>> failed; Job 'inMemoryAnalyticsJob' failed;Analytics table process failed " >>>>>>>>> >>>>>>>>> Attached are some screenshots of the message. I tried to clear >>>>>>>>> analytics tables and run analytics again but its not improving. >>>>>>>>> >>>>>>>>> The online 2.29 demo also has the same message bu with different >>>>>>>>> contents. >>>>>>>>> >>>>>>>>> Please share the hints on how i can dealt with these. As my system >>>>>>>>> has to sent out notification messages when thresholds are reached. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *Adolphe Kamugunga* >>>>>>>>> *MIS Technical Advisor* >>>>>>>>> Mobile: +250 788 740 578; >>>>>>>>> Email:kaadol@xxxxxxxxx >>>>>>>>> Skype: ka.adolphe >>>>>>>>> RWANDA >>>>>>>>> >>>>>>>>> >>>>>>>>> On 1 July 2018 at 01:04, gerald thomas <gerald17006@xxxxxxxxx> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Djibril, >>>>>>>>>> Why not try to install java 8 manually? >>>>>>>>>> >>>>>>>>>> Follow these steps: >>>>>>>>>> >>>>>>>>>> https://tecadmin.net/install-oracle-java-8-ubuntu-via-ppa/ >>>>>>>>>> >>>>>>>>>> On Sat, 30 Jun 2018 at 22:26, DJIBRIL Hakim <djib.hakim@xxxxxxxxx> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> I am setting up dhis2 instance on ubuntu 16.04 with dhis2-tools. >>>>>>>>>>> When I am running this instance and choose to view log with >>>>>>>>>>> dhis2-logtail, I got this error >>>>>>>>>>> *usr/share/tomcat7/bin/catalina.sh: 1: eval: >>>>>>>>>>> /usr/lib/jvm/java-8-oracle/jre/bin/java: not found* >>>>>>>>>>> >>>>>>>>>>> What can I do to fix it ? >>>>>>>>>>> Best >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Mailing list: https://launchpad.net/~dhis2-users >>>>>>>>>>> Post to : dhis2-users@xxxxxxxxxxxxxxxxxxx >>>>>>>>>>> Unsubscribe : https://launchpad.net/~dhis2-users >>>>>>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Gerald >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Mailing list: https://launchpad.net/~dhis2-users >>>>>>>>>> Post to : dhis2-users@xxxxxxxxxxxxxxxxxxx >>>>>>>>>> Unsubscribe : https://launchpad.net/~dhis2-users >>>>>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>>>>> >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Mailing list: https://launchpad.net/~dhis2-users >>>>>>>>> Post to : dhis2-users@xxxxxxxxxxxxxxxxxxx >>>>>>>>> Unsubscribe : https://launchpad.net/~dhis2-users >>>>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> >>>>>>>> Gerald >>>>>>>> >>>>>>> >>>>>>> -- >>>>>> Regards, >>>>>> >>>>>> Gerald >>>>>> >>>>> _______________________________________________ >>>>>> 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 >>>>>> >>>>> -- >>>> Regards, >>>> >>>> Gerald >>>> _______________________________________________ >>>> 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 >>>> >>> >>> >>> -- >>> >>> >>> *David Huser* >>> DHIS2 Support Specialist >>> dhuser@xxxxxxxxxxxxxx | https://baosystems.com | 2900 K Street, Suite >>> 507, Washington D.C. 20007 >>> >> >> >> _______________________________________________ >> 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 >> >> > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-users > Post to : dhis2-users@xxxxxxxxxxxxxxxxxxx > Unsubscribe : https://launchpad.net/~dhis2-users > More help : https://help.launchpad.net/ListHelp >
Attachment:
Posta di INFORMAPRO - [KRG Health Monitoring System] Job 'inMemoryAnalyticsJob' failed.pdf
Description: Adobe PDF document
| Thread Previous • Date Previous • Date Next • Thread Next |
