NBAM program fails when database column name > 30 bytes
Oracle only allows column names for a maximum of 30 bytes. PRPC gets around this when generating tables by truncating the name.
However, this does not occur in the auto-generated script that is produced when an NBAM program runs.
2014-09-01 11:55:15,152 [.PRPCWorkManager : 1] [ STANDARD] [ PegaNBAM:07.11] (fferBatch.System_Queue_.Action) ERROR - ProcessOfferBatch: Batch execution failed.
com.pega.pegarules.pub.PRRuntimeException: Cannot list the database
com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: 972 SQLState: 42000 Message: ORA-00972: identifier is too long
Steps to Reproduce
Create an NBAM program that uses columns whose names are > 30 bytes. Run the program.
The root cause of this problem is defect/misconfiguration in the PRPC operating environment. Some of the properties used in a custom class are 30 characters length. This causes a failure when creating the alias for the column by prefixing "C_" to column name, the length exceeds 30 character length limit of Oracle.
Use column names <=27.