Support Article

Case creation fails after migration from DB2 to Oracle



After importing a Pega application jar from Pega running on DB2 to Pega running on Oracle, case creation fails with an error.

Error Messages

Problem #1, SQLState 42000, Error code 1747: java.sql.BatchUpdateException: ORA-01747: invalid user.table.column, table.column, or column specification

Steps to Reproduce

1) Import an application from a Pega application running on DB2 to a Pega install running on Oracle.
2) Try to create a case.

Root Cause

An issue in the custom application code or rules.

The underlying issue is that properties have been named reserved Oracle keywords in an environment running on DB2 and although the migration itself did not fail when moving to an Oracle environment, the SQL calls that contain these property names are now failing because of the use of these reserved keywords.


Support for this was introduced in Pega 7.2.1 as an enhancement, however it is possible to avoid the issue by implementing one of two local changes.

Either create external mappings for these properties to use a different column name in the database than the reserved Oracle keywords

(or )

Use different property names.

Published May 16, 2017 - Updated June 5, 2017

Have a question? Get answers now.

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