Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-30 Thread gerald thomas
Dear Calle
Noted!!!



On 1/30/17, Calle Hedberg  wrote:
> Gerald,
>
> Firstly, I've verified this morning that there are no duplicates in the
> datavalue table. I was 99.9% sure of that since the primary key was in
> place, but to verify I created an exact duplicate called "datavalue2" with
> the same primary key and copied all the records across.
>
> Secondly, those errors might be log errors linked to some of the clean-up
> work we did on Thursday/Friday. The errors were probably triggered by me
> trying to insert some few data values via ODBC and failing due to those
> duplicates (i.e. no records inserted). There's no reason to be concerned
> about those.
>
> So unless those log errors should re-appear for some reason, there is no
> problem.
>
> Regards
> Calle
>
> On 30 January 2017 at 12:25, Bob Jolliffe  wrote:
>
>> Morning Gerald.  No this error would have nothing to do with importing
>> metadata or metadata that was previously imported as far as I can think.
>>
>> It is purely about duplicate reporting of data.  Usually two identical
>> rows in the batch you are importing.  Which is why I ask where you got
>> this
>> data from that you imported?  If it was data exported from another dhis2
>> system you wouldn't normally see this.  But if is from somewhere else (a
>> spreadsheet, ihris, some other system) there might be, for example,
>> duplicate orgunits in the batch.
>>
>> On 30 January 2017 at 09:54, gerald thomas  wrote:
>>
>>> Good morning all,
>>>
>>> Bob, at some point Calle was importing metadata but i don't know if
>>> that should be an issue. I am currently monitoring the logs to see if
>>> i will receive those errors again.
>>>
>>> On 1/28/17, Seid Hussein  wrote:
>>> > Hi Gerald,
>>> >
>>> > You can use the (insert if not exists) query to insert your data. But
>>> > unlike the COPY function which allows bulk insert, you have to write
>>> > an
>>> > insert statement for each data value you intend to insert.
>>> >
>>> > Regards,
>>> >
>>> >
>>> > Seid,
>>> >
>>> > On Saturday, January 28, 2017, Bob Jolliffe 
>>> wrote:
>>> >
>>> >> where does the data come from that you try to import?
>>> >>
>>> >> On 28 January 2017 at 19:55, gerald thomas >> >> > wrote:
>>> >>
>>> >>> Funnily I Bob I only copied a section of the log, I have various
>>> >>> dataelements ids & period ids which are sending those errors.
>>> >>> So I am worried where are these errors coming from now.
>>> >>>
>>> >>> On Jan 28, 2017 7:31 PM, "Bob Jolliffe" >> >>> > wrote:
>>> >>>
>>> >>> Gerald the clue is in your error message:
>>> >>>
>>> >>> Detail: Key (dataelementid, periodid,
>>> >>> sourceid,categoryoptioncomboid,
>>> >>> attributeoptioncomboid)=(1973, 2784149, 301,13, 13) already exists.
>>> >>>
>>> >>> This usually means you have duplicates among the datavalues you are
>>> >>> trying to import.  ie. more than one row with the key values as
>>> >>> shown
>>> in
>>> >>> your error message.
>>> >>>
>>> >>> On 28 January 2017 at 19:02, gerald thomas >> >>> > wrote:
>>> >>>
>>>  Seid,
>>>  Thanks for your help but how can i identify those dataelements:
>>> 
>>>  So I suggest you either to use the web API and import through the
>>>  import/export module or find out which of the metadata IDs is
>>>  duplicate and correct it.
>>> 
>>>  On 1/28/17, Seid Hussein >>  > wrote:
>>>  > Hi Gerald,
>>>  >
>>>  > I believe you're trying to import through the database rather
>>>  > than
>>>  > the
>>>  API
>>>  > which is a better option because of you've duplicate there the
>>>  > most
>>>  > probable action ta update rather than a duplicate error.
>>>  >
>>>  > Most probably what happened is you have duplicate metadata. Each
>>> data
>>>  value
>>>  > shall have a unique combination of data element id, period id,
>>>  > org
>>>  unit id,
>>>  > category option combo id, and attribute option combo id.
>>>  >
>>>  > So I suggest you either to use the web API and import through the
>>>  > import/export module or find out which of the metadata IDs is
>>>  duplicate and
>>>  > correct it.
>>>  >
>>>  > Regards,
>>>  >
>>>  >
>>>  > Seid,
>>>  >
>>>  > On Friday, January 27, 2017, gerald thomas >>  > wrote:
>>>  >
>>>  >> Dear All,
>>>  >>
>>>  >> What is the meaning of this error:
>>>  >>
>>>  >> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value
>>> violates
>>>  >> unique constraint "datavalue_pkey"
>>>  >>   Detail: Key (dataelementid, periodid, sourceid,
>>>  >> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149,
>>> 301,
>>>  >> 13, 13) already exists.
>>>  >>
>>>  >> Please find the attached copy of catalina.out log file
>>>  >>
>>>  >> --
>>>  >> Regards,
>>>  >>
>>>  >> Gerald
>>>  >>
>>>  >
>>> 
>>> 
>>>  --
>>>  Regards,
>>> 
>>>  Gerald
>>> 
>>>  _

Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-30 Thread Calle Hedberg
Gerald,

Firstly, I've verified this morning that there are no duplicates in the
datavalue table. I was 99.9% sure of that since the primary key was in
place, but to verify I created an exact duplicate called "datavalue2" with
the same primary key and copied all the records across.

Secondly, those errors might be log errors linked to some of the clean-up
work we did on Thursday/Friday. The errors were probably triggered by me
trying to insert some few data values via ODBC and failing due to those
duplicates (i.e. no records inserted). There's no reason to be concerned
about those.

So unless those log errors should re-appear for some reason, there is no
problem.

Regards
Calle

On 30 January 2017 at 12:25, Bob Jolliffe  wrote:

> Morning Gerald.  No this error would have nothing to do with importing
> metadata or metadata that was previously imported as far as I can think.
>
> It is purely about duplicate reporting of data.  Usually two identical
> rows in the batch you are importing.  Which is why I ask where you got this
> data from that you imported?  If it was data exported from another dhis2
> system you wouldn't normally see this.  But if is from somewhere else (a
> spreadsheet, ihris, some other system) there might be, for example,
> duplicate orgunits in the batch.
>
> On 30 January 2017 at 09:54, gerald thomas  wrote:
>
>> Good morning all,
>>
>> Bob, at some point Calle was importing metadata but i don't know if
>> that should be an issue. I am currently monitoring the logs to see if
>> i will receive those errors again.
>>
>> On 1/28/17, Seid Hussein  wrote:
>> > Hi Gerald,
>> >
>> > You can use the (insert if not exists) query to insert your data. But
>> > unlike the COPY function which allows bulk insert, you have to write an
>> > insert statement for each data value you intend to insert.
>> >
>> > Regards,
>> >
>> >
>> > Seid,
>> >
>> > On Saturday, January 28, 2017, Bob Jolliffe 
>> wrote:
>> >
>> >> where does the data come from that you try to import?
>> >>
>> >> On 28 January 2017 at 19:55, gerald thomas > >> > wrote:
>> >>
>> >>> Funnily I Bob I only copied a section of the log, I have various
>> >>> dataelements ids & period ids which are sending those errors.
>> >>> So I am worried where are these errors coming from now.
>> >>>
>> >>> On Jan 28, 2017 7:31 PM, "Bob Jolliffe" > >>> > wrote:
>> >>>
>> >>> Gerald the clue is in your error message:
>> >>>
>> >>> Detail: Key (dataelementid, periodid, sourceid,categoryoptioncomboid,
>> >>> attributeoptioncomboid)=(1973, 2784149, 301,13, 13) already exists.
>> >>>
>> >>> This usually means you have duplicates among the datavalues you are
>> >>> trying to import.  ie. more than one row with the key values as shown
>> in
>> >>> your error message.
>> >>>
>> >>> On 28 January 2017 at 19:02, gerald thomas > >>> > wrote:
>> >>>
>>  Seid,
>>  Thanks for your help but how can i identify those dataelements:
>> 
>>  So I suggest you either to use the web API and import through the
>>  import/export module or find out which of the metadata IDs is
>>  duplicate and correct it.
>> 
>>  On 1/28/17, Seid Hussein >  > wrote:
>>  > Hi Gerald,
>>  >
>>  > I believe you're trying to import through the database rather than
>>  > the
>>  API
>>  > which is a better option because of you've duplicate there the most
>>  > probable action ta update rather than a duplicate error.
>>  >
>>  > Most probably what happened is you have duplicate metadata. Each
>> data
>>  value
>>  > shall have a unique combination of data element id, period id, org
>>  unit id,
>>  > category option combo id, and attribute option combo id.
>>  >
>>  > So I suggest you either to use the web API and import through the
>>  > import/export module or find out which of the metadata IDs is
>>  duplicate and
>>  > correct it.
>>  >
>>  > Regards,
>>  >
>>  >
>>  > Seid,
>>  >
>>  > On Friday, January 27, 2017, gerald thomas >  > wrote:
>>  >
>>  >> Dear All,
>>  >>
>>  >> What is the meaning of this error:
>>  >>
>>  >> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value
>> violates
>>  >> unique constraint "datavalue_pkey"
>>  >>   Detail: Key (dataelementid, periodid, sourceid,
>>  >> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149,
>> 301,
>>  >> 13, 13) already exists.
>>  >>
>>  >> Please find the attached copy of catalina.out log file
>>  >>
>>  >> --
>>  >> Regards,
>>  >>
>>  >> Gerald
>>  >>
>>  >
>> 
>> 
>>  --
>>  Regards,
>> 
>>  Gerald
>> 
>>  ___
>>  Mailing list: https://launchpad.net/~dhis2-users
>>  Post to : dhis2-us...@lists.launchpad.net
>>  
>>  Unsubscribe : https://launchpad.net/~dhis2-users
>>  More help   : https://help.launchpad.net/ListH

Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-30 Thread Bob Jolliffe
Morning Gerald.  No this error would have nothing to do with importing
metadata or metadata that was previously imported as far as I can think.

It is purely about duplicate reporting of data.  Usually two identical rows
in the batch you are importing.  Which is why I ask where you got this data
from that you imported?  If it was data exported from another dhis2 system
you wouldn't normally see this.  But if is from somewhere else (a
spreadsheet, ihris, some other system) there might be, for example,
duplicate orgunits in the batch.

On 30 January 2017 at 09:54, gerald thomas  wrote:

> Good morning all,
>
> Bob, at some point Calle was importing metadata but i don't know if
> that should be an issue. I am currently monitoring the logs to see if
> i will receive those errors again.
>
> On 1/28/17, Seid Hussein  wrote:
> > Hi Gerald,
> >
> > You can use the (insert if not exists) query to insert your data. But
> > unlike the COPY function which allows bulk insert, you have to write an
> > insert statement for each data value you intend to insert.
> >
> > Regards,
> >
> >
> > Seid,
> >
> > On Saturday, January 28, 2017, Bob Jolliffe 
> wrote:
> >
> >> where does the data come from that you try to import?
> >>
> >> On 28 January 2017 at 19:55, gerald thomas  >> > wrote:
> >>
> >>> Funnily I Bob I only copied a section of the log, I have various
> >>> dataelements ids & period ids which are sending those errors.
> >>> So I am worried where are these errors coming from now.
> >>>
> >>> On Jan 28, 2017 7:31 PM, "Bob Jolliffe"  >>> > wrote:
> >>>
> >>> Gerald the clue is in your error message:
> >>>
> >>> Detail: Key (dataelementid, periodid, sourceid,categoryoptioncomboid,
> >>> attributeoptioncomboid)=(1973, 2784149, 301,13, 13) already exists.
> >>>
> >>> This usually means you have duplicates among the datavalues you are
> >>> trying to import.  ie. more than one row with the key values as shown
> in
> >>> your error message.
> >>>
> >>> On 28 January 2017 at 19:02, gerald thomas  >>> > wrote:
> >>>
>  Seid,
>  Thanks for your help but how can i identify those dataelements:
> 
>  So I suggest you either to use the web API and import through the
>  import/export module or find out which of the metadata IDs is
>  duplicate and correct it.
> 
>  On 1/28/17, Seid Hussein   > wrote:
>  > Hi Gerald,
>  >
>  > I believe you're trying to import through the database rather than
>  > the
>  API
>  > which is a better option because of you've duplicate there the most
>  > probable action ta update rather than a duplicate error.
>  >
>  > Most probably what happened is you have duplicate metadata. Each
> data
>  value
>  > shall have a unique combination of data element id, period id, org
>  unit id,
>  > category option combo id, and attribute option combo id.
>  >
>  > So I suggest you either to use the web API and import through the
>  > import/export module or find out which of the metadata IDs is
>  duplicate and
>  > correct it.
>  >
>  > Regards,
>  >
>  >
>  > Seid,
>  >
>  > On Friday, January 27, 2017, gerald thomas   > wrote:
>  >
>  >> Dear All,
>  >>
>  >> What is the meaning of this error:
>  >>
>  >> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value violates
>  >> unique constraint "datavalue_pkey"
>  >>   Detail: Key (dataelementid, periodid, sourceid,
>  >> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149, 301,
>  >> 13, 13) already exists.
>  >>
>  >> Please find the attached copy of catalina.out log file
>  >>
>  >> --
>  >> Regards,
>  >>
>  >> Gerald
>  >>
>  >
> 
> 
>  --
>  Regards,
> 
>  Gerald
> 
>  ___
>  Mailing list: https://launchpad.net/~dhis2-users
>  Post to : dhis2-us...@lists.launchpad.net
>  
>  Unsubscribe : https://launchpad.net/~dhis2-users
>  More help   : https://help.launchpad.net/ListHelp
> 
> >>>
> >>>
> >>>
> >>
> >
>
>
> --
> Regards,
>
> Gerald
>
___
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


Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-30 Thread gerald thomas
Good morning all,

Bob, at some point Calle was importing metadata but i don't know if
that should be an issue. I am currently monitoring the logs to see if
i will receive those errors again.

On 1/28/17, Seid Hussein  wrote:
> Hi Gerald,
>
> You can use the (insert if not exists) query to insert your data. But
> unlike the COPY function which allows bulk insert, you have to write an
> insert statement for each data value you intend to insert.
>
> Regards,
>
>
> Seid,
>
> On Saturday, January 28, 2017, Bob Jolliffe  wrote:
>
>> where does the data come from that you try to import?
>>
>> On 28 January 2017 at 19:55, gerald thomas > > wrote:
>>
>>> Funnily I Bob I only copied a section of the log, I have various
>>> dataelements ids & period ids which are sending those errors.
>>> So I am worried where are these errors coming from now.
>>>
>>> On Jan 28, 2017 7:31 PM, "Bob Jolliffe" >> > wrote:
>>>
>>> Gerald the clue is in your error message:
>>>
>>> Detail: Key (dataelementid, periodid, sourceid,categoryoptioncomboid,
>>> attributeoptioncomboid)=(1973, 2784149, 301,13, 13) already exists.
>>>
>>> This usually means you have duplicates among the datavalues you are
>>> trying to import.  ie. more than one row with the key values as shown in
>>> your error message.
>>>
>>> On 28 January 2017 at 19:02, gerald thomas >> > wrote:
>>>
 Seid,
 Thanks for your help but how can i identify those dataelements:

 So I suggest you either to use the web API and import through the
 import/export module or find out which of the metadata IDs is
 duplicate and correct it.

 On 1/28/17, Seid Hussein >>> > wrote:
 > Hi Gerald,
 >
 > I believe you're trying to import through the database rather than
 > the
 API
 > which is a better option because of you've duplicate there the most
 > probable action ta update rather than a duplicate error.
 >
 > Most probably what happened is you have duplicate metadata. Each data
 value
 > shall have a unique combination of data element id, period id, org
 unit id,
 > category option combo id, and attribute option combo id.
 >
 > So I suggest you either to use the web API and import through the
 > import/export module or find out which of the metadata IDs is
 duplicate and
 > correct it.
 >
 > Regards,
 >
 >
 > Seid,
 >
 > On Friday, January 27, 2017, gerald thomas >>> > wrote:
 >
 >> Dear All,
 >>
 >> What is the meaning of this error:
 >>
 >> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value violates
 >> unique constraint "datavalue_pkey"
 >>   Detail: Key (dataelementid, periodid, sourceid,
 >> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149, 301,
 >> 13, 13) already exists.
 >>
 >> Please find the attached copy of catalina.out log file
 >>
 >> --
 >> Regards,
 >>
 >> Gerald
 >>
 >


 --
 Regards,

 Gerald

 ___
 Mailing list: https://launchpad.net/~dhis2-users
 Post to : dhis2-us...@lists.launchpad.net
 
 Unsubscribe : https://launchpad.net/~dhis2-users
 More help   : https://help.launchpad.net/ListHelp

>>>
>>>
>>>
>>
>


-- 
Regards,

Gerald

___
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


Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-28 Thread Seid Hussein
Hi Gerald,

You can use the (insert if not exists) query to insert your data. But
unlike the COPY function which allows bulk insert, you have to write an
insert statement for each data value you intend to insert.

Regards,


Seid,

On Saturday, January 28, 2017, Bob Jolliffe  wrote:

> where does the data come from that you try to import?
>
> On 28 January 2017 at 19:55, gerald thomas  > wrote:
>
>> Funnily I Bob I only copied a section of the log, I have various
>> dataelements ids & period ids which are sending those errors.
>> So I am worried where are these errors coming from now.
>>
>> On Jan 28, 2017 7:31 PM, "Bob Jolliffe" > > wrote:
>>
>> Gerald the clue is in your error message:
>>
>> Detail: Key (dataelementid, periodid, sourceid,categoryoptioncomboid,
>> attributeoptioncomboid)=(1973, 2784149, 301,13, 13) already exists.
>>
>> This usually means you have duplicates among the datavalues you are
>> trying to import.  ie. more than one row with the key values as shown in
>> your error message.
>>
>> On 28 January 2017 at 19:02, gerald thomas > > wrote:
>>
>>> Seid,
>>> Thanks for your help but how can i identify those dataelements:
>>>
>>> So I suggest you either to use the web API and import through the
>>> import/export module or find out which of the metadata IDs is
>>> duplicate and correct it.
>>>
>>> On 1/28/17, Seid Hussein >> > wrote:
>>> > Hi Gerald,
>>> >
>>> > I believe you're trying to import through the database rather than the
>>> API
>>> > which is a better option because of you've duplicate there the most
>>> > probable action ta update rather than a duplicate error.
>>> >
>>> > Most probably what happened is you have duplicate metadata. Each data
>>> value
>>> > shall have a unique combination of data element id, period id, org
>>> unit id,
>>> > category option combo id, and attribute option combo id.
>>> >
>>> > So I suggest you either to use the web API and import through the
>>> > import/export module or find out which of the metadata IDs is
>>> duplicate and
>>> > correct it.
>>> >
>>> > Regards,
>>> >
>>> >
>>> > Seid,
>>> >
>>> > On Friday, January 27, 2017, gerald thomas >> > wrote:
>>> >
>>> >> Dear All,
>>> >>
>>> >> What is the meaning of this error:
>>> >>
>>> >> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value violates
>>> >> unique constraint "datavalue_pkey"
>>> >>   Detail: Key (dataelementid, periodid, sourceid,
>>> >> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149, 301,
>>> >> 13, 13) already exists.
>>> >>
>>> >> Please find the attached copy of catalina.out log file
>>> >>
>>> >> --
>>> >> Regards,
>>> >>
>>> >> Gerald
>>> >>
>>> >
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Gerald
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-us...@lists.launchpad.net
>>> 
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>>
>
___
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


Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-28 Thread Bob Jolliffe
where does the data come from that you try to import?

On 28 January 2017 at 19:55, gerald thomas  wrote:

> Funnily I Bob I only copied a section of the log, I have various
> dataelements ids & period ids which are sending those errors.
> So I am worried where are these errors coming from now.
>
> On Jan 28, 2017 7:31 PM, "Bob Jolliffe"  wrote:
>
> Gerald the clue is in your error message:
>
> Detail: Key (dataelementid, periodid, sourceid,categoryoptioncomboid,
> attributeoptioncomboid)=(1973, 2784149, 301,13, 13) already exists.
>
> This usually means you have duplicates among the datavalues you are trying
> to import.  ie. more than one row with the key values as shown in your
> error message.
>
> On 28 January 2017 at 19:02, gerald thomas  wrote:
>
>> Seid,
>> Thanks for your help but how can i identify those dataelements:
>>
>> So I suggest you either to use the web API and import through the
>> import/export module or find out which of the metadata IDs is
>> duplicate and correct it.
>>
>> On 1/28/17, Seid Hussein  wrote:
>> > Hi Gerald,
>> >
>> > I believe you're trying to import through the database rather than the
>> API
>> > which is a better option because of you've duplicate there the most
>> > probable action ta update rather than a duplicate error.
>> >
>> > Most probably what happened is you have duplicate metadata. Each data
>> value
>> > shall have a unique combination of data element id, period id, org unit
>> id,
>> > category option combo id, and attribute option combo id.
>> >
>> > So I suggest you either to use the web API and import through the
>> > import/export module or find out which of the metadata IDs is duplicate
>> and
>> > correct it.
>> >
>> > Regards,
>> >
>> >
>> > Seid,
>> >
>> > On Friday, January 27, 2017, gerald thomas 
>> wrote:
>> >
>> >> Dear All,
>> >>
>> >> What is the meaning of this error:
>> >>
>> >> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value violates
>> >> unique constraint "datavalue_pkey"
>> >>   Detail: Key (dataelementid, periodid, sourceid,
>> >> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149, 301,
>> >> 13, 13) already exists.
>> >>
>> >> Please find the attached copy of catalina.out log file
>> >>
>> >> --
>> >> Regards,
>> >>
>> >> Gerald
>> >>
>> >
>>
>>
>> --
>> Regards,
>>
>> Gerald
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-us...@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
___
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


Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-28 Thread gerald thomas
Funnily I Bob I only copied a section of the log, I have various
dataelements ids & period ids which are sending those errors.
So I am worried where are these errors coming from now.

On Jan 28, 2017 7:31 PM, "Bob Jolliffe"  wrote:

Gerald the clue is in your error message:

Detail: Key (dataelementid, periodid, sourceid,categoryoptioncomboid,
attributeoptioncomboid)=(1973, 2784149, 301,13, 13) already exists.

This usually means you have duplicates among the datavalues you are trying
to import.  ie. more than one row with the key values as shown in your
error message.

On 28 January 2017 at 19:02, gerald thomas  wrote:

> Seid,
> Thanks for your help but how can i identify those dataelements:
>
> So I suggest you either to use the web API and import through the
> import/export module or find out which of the metadata IDs is
> duplicate and correct it.
>
> On 1/28/17, Seid Hussein  wrote:
> > Hi Gerald,
> >
> > I believe you're trying to import through the database rather than the
> API
> > which is a better option because of you've duplicate there the most
> > probable action ta update rather than a duplicate error.
> >
> > Most probably what happened is you have duplicate metadata. Each data
> value
> > shall have a unique combination of data element id, period id, org unit
> id,
> > category option combo id, and attribute option combo id.
> >
> > So I suggest you either to use the web API and import through the
> > import/export module or find out which of the metadata IDs is duplicate
> and
> > correct it.
> >
> > Regards,
> >
> >
> > Seid,
> >
> > On Friday, January 27, 2017, gerald thomas 
> wrote:
> >
> >> Dear All,
> >>
> >> What is the meaning of this error:
> >>
> >> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value violates
> >> unique constraint "datavalue_pkey"
> >>   Detail: Key (dataelementid, periodid, sourceid,
> >> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149, 301,
> >> 13, 13) already exists.
> >>
> >> Please find the attached copy of catalina.out log file
> >>
> >> --
> >> Regards,
> >>
> >> Gerald
> >>
> >
>
>
> --
> Regards,
>
> Gerald
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
___
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


Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-28 Thread Bob Jolliffe
Gerald the clue is in your error message:

Detail: Key (dataelementid, periodid, sourceid,categoryoptioncomboid,
attributeoptioncomboid)=(1973, 2784149, 301,13, 13) already exists.

This usually means you have duplicates among the datavalues you are trying
to import.  ie. more than one row with the key values as shown in your
error message.

On 28 January 2017 at 19:02, gerald thomas  wrote:

> Seid,
> Thanks for your help but how can i identify those dataelements:
>
> So I suggest you either to use the web API and import through the
> import/export module or find out which of the metadata IDs is
> duplicate and correct it.
>
> On 1/28/17, Seid Hussein  wrote:
> > Hi Gerald,
> >
> > I believe you're trying to import through the database rather than the
> API
> > which is a better option because of you've duplicate there the most
> > probable action ta update rather than a duplicate error.
> >
> > Most probably what happened is you have duplicate metadata. Each data
> value
> > shall have a unique combination of data element id, period id, org unit
> id,
> > category option combo id, and attribute option combo id.
> >
> > So I suggest you either to use the web API and import through the
> > import/export module or find out which of the metadata IDs is duplicate
> and
> > correct it.
> >
> > Regards,
> >
> >
> > Seid,
> >
> > On Friday, January 27, 2017, gerald thomas 
> wrote:
> >
> >> Dear All,
> >>
> >> What is the meaning of this error:
> >>
> >> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value violates
> >> unique constraint "datavalue_pkey"
> >>   Detail: Key (dataelementid, periodid, sourceid,
> >> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149, 301,
> >> 13, 13) already exists.
> >>
> >> Please find the attached copy of catalina.out log file
> >>
> >> --
> >> Regards,
> >>
> >> Gerald
> >>
> >
>
>
> --
> Regards,
>
> Gerald
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
___
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


Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-28 Thread gerald thomas
Seid,
Thanks for your help but how can i identify those dataelements:

So I suggest you either to use the web API and import through the
import/export module or find out which of the metadata IDs is
duplicate and correct it.

On 1/28/17, Seid Hussein  wrote:
> Hi Gerald,
>
> I believe you're trying to import through the database rather than the API
> which is a better option because of you've duplicate there the most
> probable action ta update rather than a duplicate error.
>
> Most probably what happened is you have duplicate metadata. Each data value
> shall have a unique combination of data element id, period id, org unit id,
> category option combo id, and attribute option combo id.
>
> So I suggest you either to use the web API and import through the
> import/export module or find out which of the metadata IDs is duplicate and
> correct it.
>
> Regards,
>
>
> Seid,
>
> On Friday, January 27, 2017, gerald thomas  wrote:
>
>> Dear All,
>>
>> What is the meaning of this error:
>>
>> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value violates
>> unique constraint "datavalue_pkey"
>>   Detail: Key (dataelementid, periodid, sourceid,
>> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149, 301,
>> 13, 13) already exists.
>>
>> Please find the attached copy of catalina.out log file
>>
>> --
>> Regards,
>>
>> Gerald
>>
>


-- 
Regards,

Gerald

___
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


Re: [Dhis2-devs] [Dhis2-users] Tomcat error

2017-01-28 Thread Seid Hussein
Hi Gerald,

I believe you're trying to import through the database rather than the API
which is a better option because of you've duplicate there the most
probable action ta update rather than a duplicate error.

Most probably what happened is you have duplicate metadata. Each data value
shall have a unique combination of data element id, period id, org unit id,
category option combo id, and attribute option combo id.

So I suggest you either to use the web API and import through the
import/export module or find out which of the metadata IDs is duplicate and
correct it.

Regards,


Seid,

On Friday, January 27, 2017, gerald thomas  wrote:

> Dear All,
>
> What is the meaning of this error:
>
> * ERROR 2017-01-05 12:03:07,593 ERROR: duplicate key value violates
> unique constraint "datavalue_pkey"
>   Detail: Key (dataelementid, periodid, sourceid,
> categoryoptioncomboid, attributeoptioncomboid)=(1973, 2784149, 301,
> 13, 13) already exists.
>
> Please find the attached copy of catalina.out log file
>
> --
> Regards,
>
> Gerald
>
___
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