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

Customer Service 7.1.4 Import Error with TABLE PEGA.PA_RATING



When attempting to upgrade from Customer Process Manager (CPM) 6.2 SP3 to Customer Service (CS) 7.1.4, during the import of the CustomerService_714,jar, when the step to apply schema change was reached the "Automatic" option was chosen to automatically apply the schema changes.
During this phase of the import the below error occurred.

Error Messages

Error: Database-General Problem executing SQL to update database schema 955 42000 ORA-00955: name is already used by an existing object DatabaseException caused by prior exception: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object | SQL Code: 955 | SQL State: 42000

Steps to Reproduce

1. Import the CustomerService_714.jar.
2. At the schema changes screen choose "Automatic".

Root Cause

The unique constraints on four of the underlying Customer Service tables have changed between CPM 6.2 SP3 and  CS 7.1.4.
The schema change step does recognize this, drops the original constraint and tries to apply the new constraint.

In the case of an Oracle database when a new constraint is added it will also create an index with the same name.
In this instance the "drop constraint" command had only dropped the constraint itself and had left the index of the name <table name>_pk intact.

Subsequently, when it attempts to create the new constraint this will fail because the associated index name already exists.

This was shown to impact the following four tables: 


In order to overcome issue:
  1. Re-import of the CustomerService_714.sql, choosing the "Manual" option for applying the schema changes.
  2. Click on the button at the bottom of the screen to generate the CustomerService_714.sql file.
  3. Open the file and search for the four "drop constraint" command and add the equivalent "drop index" command after each drop constraint.

        4. Then apply the CustomerService_714.sql file using a native database client.
        5. And following this resume the import process in Pega.
Suggest Edit

Published June 18, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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