duplicate key value violates unique constraint

This message was edited 1 time. Last update was at 14 Aug 2009 01:56:52

Hi,

I'm using Postgres 8.3.3 and Grid 1.0 . I'm having one problem :

While loading data in to Grid table which has no primary or secondary keys on table is showing following error:

2009-08-13 22:14:40,305 - ERROR Catching throwable:
java.io.IOException: testdbN15@myserver: loader failed to load data: com.edb.util.PSQLException: SERROR^@C23505^@Mduplicate key value violates unique constraint "idx_xrowid_sample_test_240709"^@WCOPY sample_test_240709, line 7: "20090724174922_104543,NA,,112775075209,321818020471498,,,,,,,,,,,,20090724,987174138,20090724,11220153..."^@Fnbtinsert.c^@L298^@R_bt_check_unique^@^@
at com.edb.gridsql.engine.loader.EDBWriter.stopEDBCopyThread(Unknown Source)
at com.edb.gridsql.engine.loader.EDBWriter.finish(Unknown Source)
at com.edb.gridsql.engine.loader.DataProcessorThread.finishLoad(Unknown Source)
at com.edb.gridsql.engine.loader.Loader.finishLoad(Unknown Source)
at com.edb.gridsql.parser.SqlCopyData.execute(Unknown Source)
at com.edb.gridsql.engine.ExecutableRequest.execute(Unknown Source)
at com.edb.gridsql.engine.XDBSessionContext.executeRequest(Unknown Source)
at com.edb.gridsql.engine.ServerStatement.execute(Unknown Source)
at com.edb.gridsql.engine.ServerStatement.execute(Unknown Source)
at com.edb.gridsql.engine.XDBSessionContext.executeRequest(Unknown Source)
at com.edb.gridsql.protocol.PgProtocolSession.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)

If any one have idea why this problem persists please guide me where to check to clear this problem.

Thanks,
Venkat

can you send the output of :

\d sample_test_240709

SELECT conname,contype,relname FROM pg_constraint ,pg_class WHERE pg_constraint.conrelid=pg_class.oid AND pg_constraint.conname='idx_xrowid_sample_test_240709';

From the original error message, it looks like the result of adding new rows was a unique constraint violation.

Regards,

Mason Sharp