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

CPM - Cannot submit any interaction with work objects



When submitting an interaction, a database error occurs and can not proceed further.

Error Messages

On Screen:

In log file:

2015-03-24 16:42:05,897 [%2F10.5.88.7-8080-29] [1_WorkTab6] [                    ] [        G2A:02.02.02] (  internal.access.DatabaseImpl) ERROR host_name|xx.x.xx.xx X06200 - Encountered problem when performing a Commit ORA-00904: "INPUTS"."TYPES#1": invalid identifier 
Caused by SQL Problems. 
Problem #1, SQLState 42000, Error code 904: java.sql.BatchUpdateException: ORA-00904: "INPUTS"."TYPES#1": invalid identifier 
Problem #2, SQLState 42000, Error code 904: java.sql.SQLSyntaxErrorException: ORA-00904: "INPUTS"."TYPES#1": invalid identifier 

Steps to Reproduce

1) Have an exposed column ending with #1.
2) Create the related external mapping on class definition.
3) Create and update a work case.

Root Cause

The root cause is unknown. The '#' character is a valid column name in Oracle. 


Developers have overcome this issue by renaming all columns #n by _n and updated all external mappings in the classes to reflect the new column names. Once done, the update of the work object works correctly.

Published March 30, 2015 - 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