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

Rename, Delete, and Copy wizards fail with pyCommitError



The Rename a Class, Delete a Class, and Copy/Merge Ruleset wizards fail with pyCommitError in Designer Studio.

Error Messages

pyCommitError - using an insert failed

Steps to Reproduce

Run the Rename a Class, Delete a Class, or Copy/Merge Ruleset wizard.

Root Cause

A defect or configuration issue in the operating environment.
After upgrading from Pega 7.1 to Pega 7.3 there are two databases, one for PegaRules and another for PegaData. The pyID is generated from one database running the store procedue sppc_data_uniqueid_withouttran and getting pyLastReservedID from the table pc_data_uniqueid. This ID was then inserted in the pc_work_accel table in the other database. There was a mismatch between these tables.


Perform the following local-change:

Update the pyLastReservedId column in pc_data_uniqueid table to a number higher than that of pyID column in the pc_work_accel table.



Published September 19, 2018 - 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