Support Article
Primary key error during install or upgrade of PMF
SA-412
Summary
Upgrade fails for Pega Management Framework (PMF) from 63 to 71.
Error Messages
**Date and time**,599 [ test-01] [ STANDARD] [ PegaRULES:07.10] (ternal.util.SchemaImporterTool) ERROR [email protected] - SQL : ALTER TABLE TEST.PPM_RELATEDITEMCOUNTS ADD CONSTRAINT PPM_RELATEDITEMCOUNTS_PK PRIMARY KEY (PZINSKEY, PXOBJCLASS)
com.pega.pegarules.pub.database.DatabaseException: Database-General Problem executing SQL to update database schema 2260 42000 ORA-02260: table can have only one primary key
From: (BB6E9DCC94F64CBF6C4A778A0D0D1F332)
SQL: ALTER TABLE TEST.PPM_RELATEDITEMCOUNTS ADD CONSTRAINT PPM_RELATEDITEMCOUNTS_PK PRIMARY KEY (PZINSKEY, PXOBJCLASS)
Caused by SQL Problems.
Problem #1, SQLState 42000, Error code 2260: java.sql.SQLSyntaxErrorException: ORA-02260: table can have only one primary key
at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:167)
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeDBSchemaDDL(DatabaseImpl.java:7340)
Root Cause
Pega system admin had quit out of Pega during PMF import and JAR upgrade. TEST.PPM_RELATEDITEMCOUNTS table was created. Upgrade, when tried another time, failed with an exception.
Composite primary key pzinskey and pxobjclass already existed in the table before the upgrade of primary key violation error was thrown.
Resolution
Delete PPM_RELATEDITEMCOUNT table, and upgrade.
Published March 27, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.