SA-8090

Summary

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 
com.pega.pegarules.pub.database.DatabaseException: 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 
    at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:289) 
    at com.pega.pegarules.data.internal.access.ConnectionStatementStore.executeBatchForAllStatements(ConnectionStatementStore.java:200) 
    at com.pega.pegarules.data.internal.access.ThreadConnectionStoreImpl.executeOutstandingBatches(ThreadConnectionStoreImpl.java:269) 

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. 

Resolution

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.