appears twice in primary key constraint
Victor Pérez Juárez
I am execute a dbcopy to migrate from ORacle to PostgreSQL but I get
this error when is create prymary key
org.postgresql.util.PSQLException: ERROR: column "ad_client_id" appears
twice in primary key constraint
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1512)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1297)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:430)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:332)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:278)
at
net.sourceforge.squirrel_sql.plugins.dbcopy.util.DBUtil.executeUpdate(DBUtil.java:257)
at
net.sourceforge.squirrel_sql.plugins.dbcopy.CopyExecutor.createTable(CopyExecutor.java:688)
at
net.sourceforge.squirrel_sql.plugins.dbcopy.CopyExecutor._execute(CopyExecutor.java:160)
at
net.sourceforge.squirrel_sql.plugins.dbcopy.CopyExecutor.access$000(CopyExecutor.java:57)
at
net.sourceforge.squirrel_sql.plugins.dbcopy.CopyExecutor$1.run(CopyExecutor.java:120)
at java.lang.Thread.run(Thread.java:595)
What is the problem?
Victor Perez
CEO
www.e-evolution.com
victor...@e-evolution.com
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
Oliver Jowett
> Hi very body!
>
> I am execute a dbcopy to migrate from ORacle to PostgreSQL but I get
> this error when is create prymary key
>
> org.postgresql.util.PSQLException: ERROR: column "ad_client_id" appears
> twice in primary key constraint
You should probably ask the authors of dbcopy as this appears to be a
client/application problem, not a JDBC driver problem -- dbcopy is
apparently creating a bogus CREATE TABLE / ADD CONSTRAINT query.
-O
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?