Skip to main content
LinkedIn
Copied!

Table of Contents

Troubleshooting ORA-02443, ORA-02429, ORA-06512, Oracle optimization issues after upgrading

This content applies only to On-Premises Services environments.

Symptoms

The issue described in this article can occur in all upgrade or update scenarios for Pega Platform™, releases prior to Pega 8.5.4. This issue is fixed in Pega 8.5.4 (coming soon).

DDL generated for an upgrade or update to Pega 8.5.1 throws an error during installation.

The following ALTER statement causes the error:

ALTER TABLE PC_ASSIGN_WORKBASKET DROP CONSTRAINT GETNEXTWORKINWORKGROUP

/

The DROP CONSTRAINT statement causes this error:

ERROR at line 1: ORA-02443: Cannot drop constraint - nonexistent constraint

The error caused by the DROP CONSTRAINT statement indicates that the constraint does not exist. Upon investigation, the user discovered that GETNEXTWORKINWORKGROUP is a functional index and not a constraint. Therefore, the user tried using the DROP INDEX statement but received the following error:

ERROR at line 1:

ORA-02429: cannot drop index used for enforcement of unique/primary key

ORA-06512: at line 5

Errors

A series of errors occur as shown in the following examples:

ALTER TABLE PC_ASSIGN_WORKBASKET DROP CONSTRAINT GETNEXTWORKINWORKGROUP

/

ERROR at line 1: ORA-02443: Cannot drop constraint - nonexistent constraint

ERROR at line 1:

ORA-02429: cannot drop index used for enforcement of unique/primary key

ORA-06512: at line 5

Explanation

Under certain circumstances the Oracle database enforces the primary key constraint for a table by using an index that is not the primary key index. This is an optimization that Oracle makes to reduce the number of unnecessary indices. However, this optimization confuses the Pega upgrade scripts and causes the upgrade (or update) to fail with the following error:

ALTER TABLE PC_ASSIGN_WORKBASKET DROP CONSTRAINT GETNEXTWORKINWORKGROUP

ERROR at line 1: ORA-02443: Cannot drop constraint - nonexistent constraint

When this happens, Oracle enforces the Primary Key (PK) constraint using the

GETNEXTWORKINWORKGROUP index, which is different from the index specified by the Pega Platform when it is shipped.

 

Solution

Best Practice: Keep current with Pega

This issue is fixed in Pega 8.5.4 (coming soon).

If you cannot update or upgrade to the latest Pega Platform Patch Release, at minimum Pega 8.5.4, and you need to keep using a Pega Platform release prior to Pega 8.5.4, complete the following steps for your Oracle database before you attempt to run the installation for an Pega Platform upgrade or update:

  1. Drop the primary key constraint on the table.
  2. Drop the index that was used to optimize.
  3. Add the primary key constraint back.
  4. Add the index back.

 

Did you find this content helpful?

100% found this useful

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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