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

Upgrade failing attempting to reference a fully qualified table



Using the Pega provided shell script, the upgrade fails. The upgrade process throws an error suggesting it is attempting to reference a fully qualified table that does not exist.

Error Messages Database-General Problem executing lock delete 942 42000 ORA-00942: table or view does not exist

From: (unknown)
SQL: delete from PRPC54.pr_sys_locks where pxSystemName = ? and pxSystemNode = ?
SQL Inserts: <pega> <95757bc692332f8881e727bd719b89c2>

Caused by SQL Problems.
Problem #1, SQLState 42000, Error code 942: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

Steps to Reproduce

Copy 5.4 version of database tables
Change ownership of the tables on database restore remapping schema PRPC54 to PRPC61
Execute the script

Root Cause

The root cause of this problem is defect/misconfiguration in the PRPC operating environment.
Within the existing PRPC system many DATA-ADMIN-DB-TABLE rules had been updated to contain the schema name PRPC54. This worked fine as long as the schema name is PRPC54.  As part of the upgrade process, the admin copied the existing database schema PRPC54 to a new schema PRPC61 but the rules within the system still held references to the old schema PRPC54.


1. Export current environment (5.4) with schema owner PRPC54 (We do not want to modify anything in the current production environment in case upgrade does not go successfully.)

2. Import (5.4) into new database leaving the schema owner PRPC54 and executing the upgrade process.

3. Start the newly upgraded environment (6.1 SP2) using the existing PRPC54 schema owner.

4. Open PRPC web and remove any references to PRPC54 in Schema Name associated with any DATA-ADMIN-DB-TABLE rules.

5. Shutdown system, export database, import into new database with PRPC61 as the owner.

6. Modify configuration files to point to the new database.
Suggest Edit

Published June 12, 2015 - Updated October 8, 2020

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