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

Rules upgrade failed during upgrade to Pega 8.2.1



As the first step in the out-of-place upgrade, the Migrate script is fails when cloning the Rules tables and the pr_data_admin table to the new Rules schema.

Error Messages

[java] (SQLLoaderInternal) INFO - Failed to execute SQL in file POSTGRES04920.sql
[java] org.postgresql.util.PSQLException: ERROR: relation "pxinsnameindex" already exists
[java] at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(

Steps to Reproduce

Run the Migrate script.

Root Cause

A defect or configuration issue in the operating environment.
An index named pxinsnameindex was added to the pr_data_admin table and the same name was used for an index on a table in the Rules schema. Neither of the indexes were provided out-of-the-box. For this script, a copy of the pr_data_admin table was created in the new Rules schema. The upgrade failed since an index was already present by that name.


Perform the following local-change: 
  1. Drop the pxinsnameindex from the pr_data_admin table.
  2. Restart the Migrate script.

Published August 15, 2019 - Updated December 2, 2021

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