Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Rule import fails with duplicate key exception



Rule-Admin-Product import fails with a duplicate key error. However, when the same Rule-Admin-Product is imported again, it works.

Error Messages

ERROR | WorkManager.PRPCWorkManager_WM : 17 | : | internal.access.DatabaseImpl | Msg: Encountered problem replacing instances in the database Database-General -803 23505 AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE INDEX IN INDEX SPACE PRRS1F8G CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X'0000027155'.. SQLCODE=-803, SQLSTATE=23505, DRIVER=4.15.94

Steps to Reproduce

Try to import a Rule-Admin-Product.

Root Cause

A defect or configuration issue in the operating environment. If batching for imports is on, Pega will use the Java Database Connectivity (JDBC) batch operations to import a Rule-Admin-Product. This leads to errors in the Rule-Admin-Product import.


Perform the following local-change:
If prconfig.xml has an entry in the form of database\databases\database_name\batchUpdates, set it to -1. 
Otherwise, set the Dynamic system Setting Pega-Engine • prconfig/database/batchupdates/default to -1.
The -1 value turns off batching, which prevents the initial failure.

Published February 11, 2016 - Updated October 8, 2020

Was this useful?

50% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us