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

Unique constraint violated during BIX Extract



When running multiple extracts using agents and pxExtractDataWithArgs at the same time, a unique constraint violation error is produced in the logs. Despite this error, the extract still seems to complete successfully.

Error Messages

2016-02-19 13:07:02,437 [.PegaWorkManager : 8] [ ] [Application:01.01.01] ( internal.access.ExtractImpl) ERROR - Error while getting the sequenceNumberORA-00001: unique constraint (PegaDataSchema.PR_LOG_PK) violated

Steps to Reproduce

Create agents that call pxExtractDataWithArgs at the same time, each running its own extract rule.

Root Cause

This occurs because the extracts are running at the same time and an entry is added to the pr_log table when each extract starts. The pzInsKey for two extracts that run at the same time is identical, thus leading to this error.


To avoid this, stagger the start times of the extracts.

Published March 5, 2016 - Updated October 8, 2020

Was this useful?

0% 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