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

Campaigns are not executed after it is created and scheduled

SA-55705

Summary



Campaigns are not executed after it is created and scheduled. The ProcessProgramRun agent is not retrieving the campaign instance for execution. 


Error Messages



[.PegaWorkManager : 9] [  STANDARD] [   ] [ PegaDSM:01.01.01] (able.Pega_DM_Batch_Work.Action) ERROR   - pzCreateBatchTable - Batch table creation failed stack trace 
com.pega.pegarules.pub.database.DatabaseException: Database-General    Problem executing SQL to update database schema    972    42000    ORA-00972: identifier is too long
DatabaseException caused by prior exception: java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long

 | SQL Code: 972 | SQL State: 42000

at com.pega.pegarules.data.internal.access.ExceptionInformation.createAppropriateExceptionDueToDBFailure(ExceptionInformation.java:354) ~[prprivate.jar:?]
    at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:333) ~[prprivate.jar:?]
    at com.pega.pegarules.data.internal.access.DBSchemaDDLExecutor.executeDBSchemaDDL(DBSchemaDDLExecutor.java:149) ~[prprivate.jar:?]
    at com.pega.pegarules.data.internal.access.DBSchemaDDLExecutor.executeDBSchemaUpdates(DBSchemaDDLExecutor.java:491) ~[prprivate.jar:?]
    at com.pega.pegarules.data.internal.access.DatabaseImpl.executeDBSchemaUpdates(DatabaseImpl.java:3529) ~[prprivate.jar:?]
    at com.pegarules.generated.activity.ra_action_pzcreatebatchtable_f76942e699492ab60f36c69114f31451.step1_circum0(ra_action_pzcreatebatchtable_f76942e699492ab60f36c69114f31451.java:241) ~[?:?]


Steps to Reproduce

  1. Log in to the application
  2. Create a Campaign
  3. Run the case


Root Cause



A defect or configuration issue in the operating environment. Campaign was unable to create tables because of the long column or property names.


Resolution

Perform the following local-change: 

Block the offending rules. 

However, if the properties are required then make the properties transient.

Alternatively, upgrade database to Oracle 12c R2 or newer.
 

 

Suggest Edit

Published July 23, 2018 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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