Support Article
Campaign run hangs at running state
Summary
Campaign stucks in running state when given wait time on Email shape with Pega Marketing 7.13.
Error Messages
java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long
CDHXD.MKT_PROSPECTS C ON ( ( R.CustomerID = C.CUSTOMERID ) ) LEFT OUTER JOIN CDHXD.MKT_CONTACT_SUMMARY CS ON ( ( R.CustomerID = CS.CustomerID ) ) WHERE (R.FLOWSTATUS = 'Wait' AND R.WAITEXPIRATIONTIME <= current_timestamp ) ORDER BY R.CustomerID, R.BundleName, R.BundleParent desc, R.pxRank
java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)
] (fferBatch.System_Queue_.Action) ERROR - ProcessOfferBatch: Batch execution failed. java.lang.Throwable: com.pega.pegarules.pub.PRRuntimeException: Cannot list the database
at com.pegarules.generated.activity.ra_action_processofferbatch_395384499f5b16d3ce1768b3d6273cbc.step34_circum0(ra_action_processofferbatch_395384499f5b16d3ce1768b3d6273cbc.java:3331)
at com.pegarules.generated.activity.ra_action_processofferbatch_395384499f5b16d3ce1768b3d6273cbc.perform(ra_action_processofferbatch_395384499f5b16d3ce1768b3d6273cbc.java:753)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3505)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10563)
Steps to Reproduce
1. Configure a campaign in which offers are sent through email.
2. On Email shape utility give a wait time.
3. Run the campaign.
Root Cause
User configured properties in top level SR class, which is having more than 28 characters.
So in ExcecuteProgramRun flow, when it is checking for any offers in wait , it is fetching data from BatchOutPR table, it is throwing identifier too long exception.
Resolution
Create a sample application with properties less that 27 characters and tested. It is working fine in this case.
So user is suggested to reduce the length of the property name in their application.
Published July 5, 2017 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.