Support Article
pyCommitError and DatabaseException observed in PMF environment
SA-2127
Summary
Users has observed pyCommitError on the screen while processing work item and has observed DatabaseException in the PegaRULES log file.
Error Messages
Following error manifests on the user screen -
Following error traces were observed in the PegaRULES log file -
2014-10-08 01:50:39,866 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ PegaRULES:07.10] (internal.context.RuleUsageImpl) INFO - Starting RuleUsage snapshot: recent
2014-10-08 01:51:05,486 [ PegaRULES-Batch-4] [ STANDARD] [ ] [ PegaRULES:07.10] (internal.context.RuleUsageImpl) ERROR - Error committing RuleUsage snapshot recent
com.pega.pegarules.pub.database.DatabaseException: Database-Saver-InsertUpdatefail
From: (B06C475EBE0456C0A2E1FC8E9F1B915D1)
SQL: insert into RULES.pr4_log_rule_usage_details (PXASSEMBLYCACHEKEY , PXCLASSNAME , PXCREATEDATETIME , PXDETAILINDEX , PXINSNAME , PXOBJCLASS , PXPARENTRULEUSAGEKEY , PXSYSTEMNODE , PXUPDATEDATETIME , PXUSECOUNT , PYLABEL , pzInsKey) values (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)
SQL Inserts: <RULE-HTML-PROPERTY|PEGAPROJMGMT-WORK-USERSTORY!URLENCODEDVALUE;STREAM|PegaRULES!07.10$b7f6c81c8977b824e61b3c84624624cc> <com.pegarules.generated.html_property.ra_stream_urlencodedvalue_2ffdb35e79acc6ddc9fe990be167c4c9> <2014-10-08 01:50:50.651> <55> <6444C08C9F46503FDC95460C7E79EAC1!COM.PEGARULES.GENERATED.HTML_PROPERTY.RA_STREAM_URLENCODEDVALUE_2FFDB35E79ACC6DDC9FE990BE167C4C9!RECENT!55> <Log-RuleUsage-Details> <LOG-RULEUSAGE 6444C08C9F46503FDC95460C7E79EAC1!COM.PEGARULES.GENERATED.HTML_PROPERTY.RA_STREAM_URLENCODEDVALUE_2FFDB35E79ACC6DDC9FE990BE167C4C9!RECENT> <6444c08c9f46503fdc95460c7e79eac1> <2014-10-08 01:50:50.651> <5> <recent> <LOG-RULEUSAGE-DETAILS 6444C08C9F46503FDC95460C7E79EAC1!COM.PEGARULES.GENERATED.HTML_PROPERTY.RA_STREAM_URLENCODEDVALUE_2FFDB35E79ACC6DDC9FE990BE167C4C9!RECENT!55>
Caused by SQL Problems.
Problem #1, SQLState 57011, Error code -968: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-968, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.9.78
at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:196)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.addBatch(DatabasePreparedStatementImpl.java:719)
at com.pega.pegarules.data.internal.access.Saver.saveAltOp(Saver.java:1374)
at com.pega.pegarules.data.internal.access.StatementOperationStore.performAltOps(StatementOperationStore.java:136)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.addBatch(DatabasePreparedStatementImpl.java:703)
at com.pega.pegarules.data.internal.access.Saver.saveNewInstanceWithNoDeletedColumnNotOnlyIfNew(Saver.java:1112)
at com.pega.pegarules.data.internal.access.Saver.saveInstance(Saver.java:840)
at com.pega.pegarules.data.internal.access.DatabaseImpl.performOps(DatabaseImpl.java:3013)
at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2419)
at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2269)
at com.pega.pegarules.data.internal.access.DatabaseImpl.commit(DatabaseImpl.java:2009)
at com.pega.pegarules.monitor.internal.context.RuleUsageImpl.updateSnapshot(RuleUsageImpl.java:339)
at com.pega.pegarules.session.internal.mgmt.Executable.updateRuleUsageSnapshot(Executable.java:7699)
at com.pegarules.generated.activity.ra_action_ruleusagesnapshot_8acf7559930ab416e0609201cc19c6af.step1_circum0(ra_action_ruleusagesnapshot_8acf7559930ab416e0609201cc19c6af.java:177)
at com.pegarules.generated.activity.ra_action_ruleusagesnapshot_8acf7559930ab416e0609201cc19c6af.perform(ra_action_ruleusagesnapshot_8acf7559930ab416e0609201cc19c6af.java:69)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3265)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(QueueProcessor.java:721)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:602)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:884)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1192)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:930)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:829)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:617)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991)
at com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532)
at java.lang.Thread.run(Thread.java:724)
Caused by: com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-968, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.9.78
at com.ibm.db2.jcc.am.fd.a(fd.java:679)
at com.ibm.db2.jcc.am.fd.a(fd.java:60)
at com.ibm.db2.jcc.am.fd.a(fd.java:127)
at com.ibm.db2.jcc.am.en.b(en.java:2222)
at com.ibm.db2.jcc.am.en.c(en.java:2205)
at com.ibm.db2.jcc.t4.cb.k(cb.java:355)
at com.ibm.db2.jcc.t4.cb.a(cb.java:61)
at com.ibm.db2.jcc.t4.q.a(q.java:50)
at com.ibm.db2.jcc.t4.sb.b(sb.java:218)
at com.ibm.db2.jcc.am.fn.nc(fn.java:2888)
at com.ibm.db2.jcc.am.fn.b(fn.java:3826)
at com.ibm.db2.jcc.am.fn.ec(fn.java:738)
at com.ibm.db2.jcc.am.fn.executeUpdate(fn.java:717)
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.executeUpdate(DatabasePreparedStatementImpl.java:483)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.addBatch(DatabasePreparedStatementImpl.java:609)
... 21 more
Steps to Reproduce
Process work object.
Root Cause
Database volume was full and this was causing the buffer pool failures.
Resolution
Removing old archive logs and adding additional space to database volume has resolved the issue.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.