Question
HSBC
IN
Last activity: 7 Aug 2023 10:32 EDT
Error encountered while upgrading to pega 8.8.1 from pega 7.4
Hi,
We have encountered an error while running upgrade.sh script.
[java] 2023-03-14 17:57:06,129 [ main] [ ] [ ] [ ] ( internal.loaders.FastLoader) ERROR - Encountered batch element exception: [java] org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "pr4_rule_vw_pk" [java] Detail: Key (pzinskey)=(RULE-ADMIN-SYSTEM-SETTINGS PEGA-PROCOM BULKPROCESSTRANSFERFLOWACTION #20141110T145849.091 GMT) already exists. [java] at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565) ~[postgresql-42.2.25.jar:42.2.25]
as it exists already it should be skipped, instead it is throwing the error.
Hi,
We have encountered an error while running upgrade.sh script.
[java] 2023-03-14 17:57:06,129 [ main] [ ] [ ] [ ] ( internal.loaders.FastLoader) ERROR - Encountered batch element exception: [java] org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "pr4_rule_vw_pk" [java] Detail: Key (pzinskey)=(RULE-ADMIN-SYSTEM-SETTINGS PEGA-PROCOM BULKPROCESSTRANSFERFLOWACTION #20141110T145849.091 GMT) already exists. [java] at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2565) ~[postgresql-42.2.25.jar:42.2.25]
as it exists already it should be skipped, instead it is throwing the error.
[java] 2023-03-14 17:57:06,133 [ main] [ ] [ ] [ ] ( internal.loaders.FastLoader) ERROR - Unable to save instance of type Data-Rule-Summary with key RULE-ADMIN-SYSTEM-SETTINGS PEGA-WB PEGAPDNQUERYURI #20180713T135043.110 GMT [java] [SHUTDOWN]-----LogManager.shutdown() [java] hasShutDowntrue [java] 2023-03-14 17:57:06,206 (com.pega.pegarules.internal.bootstr) SEVERE - Problem during method invocation (main) [java] [java] com.pega.pegarules.pub.PRException: There were 58 instances that were not imported.
Pegasystems Inc.
IN
@ShaileshM8480 It seems its trying to insert a record and fails because of unique constraint. If this issue still exists, i request you to open a support ticket and attach the complete update logs for analysis.