SA-38079

Summary

User has configured a campaign to run every month. The campaign execution fails.

Error Messages

Below error appears in the log :-

Error on node [] com.pega.dsm.dnode.api.dataflow.StageException: Exception in stage: BatchOutPR123_VC at com.pega.dsm.dnode.api.dataflow.DataFlowStage$StageOutputSubscriber.onError(DataFlowStage.java:394) at com.pega.dsm.dnode.api.dataflow.DataFlowStageProcessor.onError(DataFlowStageProcessor.java:48) at com.pega.dsm.dnode.api.dataflow.DataFlowStage$StageInputSubscriber.onError(DataFlowStage.java:286) at

Caused by: com.pega.pegarules.pub.PRRuntimeException: Cannot insert records to database Message: BatchUpdateException: ORA-12899: value too large for column "PEGA_NBAM"."BATCHOUTPR365_VC"."PRIMARYCONTACTDETAILS" (actual: 33, maximum: 32) Message: SQLException: ORA-12899: value too large for column "PEGA_NBAM"."BATCHOUTPR365_VC"."PRIMARYCONTACTDETAILS" (actual: 33, maximum: 32) at com.pega.dsm.dnode.impl.dataset.database.DatabaseSaveOperation.insertBatch(DatabaseSaveOperation.java:325) at com.pega.dsm.dnode.impl.dataset.database.DatabaseSaveOperation.access$400(DatabaseSaveOperation.java:63) at com.pega.dsm.dnode.impl.dataset.database.DatabaseSaveOperation$1.executeExposedLogic(DatabaseSaveOperation.java:120) at com.pega.dsm.dnode.impl.dataset.database.DatabaseOperationsUtil$2.emit(DatabaseOperationsUtil.java:148) ... 18 more

Caused by: java.sql.BatchUpdateException: ORA-12899: value too large for column "PEGA_NBAM"."BATCHOUTPR123_VC"."PRIMARYCONTACTDETAILS" (actual: 33, maximum: 32) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10345) at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:230) at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.executeBatch(DatabasePreparedStatementImpl.java:534) at com.pega.dsm.dnode.impl.dataset.database.DatabaseSaveOperation.insertBatch(DatabaseSaveOperation.java:321) ... 21 more

Steps to Reproduce

Run a Campaign in Pega Marketing with Segment having user's contacts with longer characters (32 characters).

Root Cause

The property PRIMARYCONTACTDETAILS did not have a "Max Length" set.

As a result in the BatchOUTPR table the corresponding column size defaulted to 32 bytes.

The column 'PRIMARYCONTACTDETAILS' was attempted to populate with larger data when the property was set with a value larger than 32 characters.

Resolution

Modify the Property PRIMARYCONTACTDETAILS and increase "Max length".