PRPC 61 to Pega 7.2 rule upgrade faile with unique constraint PR_INDEX_REFERENCE_PK violated error
As part of the upgrade from PRPC 6.x to Pega 7 rules upgrade is failed with the following error.
[java] 2016-05-23 15:09:52,671 [ main] [ ] [ ] ( internal.loaders.FastLoader) ERROR - Encountered batch element exception:
[java] java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (RULES.PR_INDEX_REFERENCE_PK) violated
[java]
[java] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
[java] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
[java] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
[java] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
[java] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
[java] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
IN
The main reason for this issue is PegaUVU ruleset got refactored as Pega-UVU in Pega 7.1.8 included in the base product, in old release customers need to import this ruleset separately.
As Upgrade process is removing only Pega- references as shown below not removing any PegaUVU ruleset references, So when it is trying to import the index references it is failing with unique constraint error as both the PegaUVU and Pega-UVU has the same pzinskey.
As a work around you can remove the PegaUVU releated records in the PR_INDEX_REFERENCE table before you trigger the upgrade.
delete from pr_index_reference where pxreferencingrulesetname like'PegaUVU%'
TCS
GB
Thanks Dhev for working with us on troubleshoot.
Another problem is , The error logging also did not correctly identify the record that was causing Duplicate entries with PZINSKEY in the PR_INDEX_REFERENCE. The logs was reporting a record ( as problematic ) but actually did not have any problem. So, error logging mechanism as well need to be revisited by Pega.
As a dirty workaround for identifying the problem record, we removed Unique constraint & index on the table and resume the upgrade. The upgrade completed. We ran a GROUP by query on PZINSKEY on the table to identify the exact problematic record.
As suggested, we will remove all the entries related to PegaUVU, then apply back the unique constraint & index and proceed further with Rule object migration.
Until Pega fixes this bug, We will also keep in mind to clean up the PegaUVU entries before the upgrade in subsequent environments.
Infosys
IN
Hi-
After executing the delete command, we are getting the same error:
2016-08-31 06:11:08,492 [ main] [ ] [ ] ( internal.loaders.FastLoader) ERROR - Encountered batch element exception:
[java] java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PEGA_AE_DEVA_RULES.PR_INDEX_REFERENCE_PK) violated
Please let us know how to proceed further. Help is highly appreciated.
Infosys Limited
IN
Hi,
If you are getting the same error even after executing the delete command, as a workaround please truncate the table PR_INDEX_REFERENCE and then run the upgrade.
Note- Please take backup of corresponding table before truncating it. Reimport customer specific instances if any into the table after successful upgrade.