Unique key constraint violation violated

Niels Nes Niels.Nes at cwi.nl
Fri Dec 28 12:25:06 CET 2012


On Fri, Dec 28, 2012 at 02:04:52AM -0800, Tapomay Dey wrote:
> Confirmed that it occurs even with MonetDataSource.
> Also tried switching to July12 SP2.
> 
> Need pointers to diagnosing it further.
> Any ideas?

To beable to debug this problem we need a 'script' which triggers the
bug. Given you setup this probably isn't very easy.

Niels
> 
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> From: Tapomay Dey <tapomay at yahoo.com>
> To: "developers-list at monetdb.org" <developers-list at monetdb.org>
> Sent: Thursday, December 27, 2012 9:15 PM
> Subject: Unique key constraint violation violated
> 
> Is this a known issue that you are working on? If so please give me the
> bug id where I would know when its fixed.
> 
> The case is as follows:
> I have a table with 32 columns with unique key on 3 of them.
> I am running live ETLs for putting data into monetdb. These ETLs are
> generating sql insert scripts.(inserts/updates/ddls)
> Using JDBC and c3p0 connection pooling.
> Have developed an external wrapper module to achieve master-master
> replication.
> One common consistency check would be a count*.
> 
> Observation:
> Queries are run in batches of 100 inserts clubbed into a single insert.
> I do a select count(*) after each batch of 100.
> After running 9100 queries the count* on one DB was 9100 but in the
> other was 9200.
> The second DB had 100 records that were duplicates of 8901-9000.
> It means when I inserted 9001 to 9100 the previous batch went into the
> store again with it and somehow surpassed the unique key constraint
> check.
> I have also observed another case where count(*) gave less results than
> actual no. of rows in the DB.
> 
> REQUEST:
> Just want to confirm if such kind of issues are part of active
> development.
> Otherwise it would be really difficult for me to push monetdb usage
> into production.
> 
> Will try again with MonetDataSource instead of c3p0. But I doubt if the
> issues are client side or connection-related.
> Plz note that the keys for which this occurs is random and thus I
> concluded it's not a data issue.
> 
> Regards,
> Tapomay Dey.
> Software Design Engg.
> Sokrati Inc.
> Email: tapomayATsokratiDOTcom
> 
> _______________________________________________
> developers-list mailing list
> developers-list at monetdb.org
> http://mail.monetdb.org/mailman/listinfo/developers-list
> 
> 

> _______________________________________________
> developers-list mailing list
> developers-list at monetdb.org
> http://mail.monetdb.org/mailman/listinfo/developers-list


-- 
Niels Nes, Centrum Wiskunde & Informatica (CWI)
Science Park 123, 1098 XG Amsterdam, The Netherlands
room L3.14,  phone ++31 20 592-4098 	sip:4098 at sip.cwi.nl
url: http://www.cwi.nl/~niels   e-mail: Niels.Nes at cwi.nl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://www.monetdb.org/pipermail/developers-list/attachments/20121228/2d1a8246/attachment.sig>
-------------- next part --------------
_______________________________________________
developers-list mailing list
developers-list at monetdb.org
http://mail.monetdb.org/mailman/listinfo/developers-list


More information about the developers-list mailing list