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

SystemCleaner agents causes system crash

SA-18209

Summary



SystemCleaner agent causes system crash in Pega 7.1.7.


Error Messages



2015-12-13 23:52:27,972 [.PRPCWorkManager : 4] [  STANDARD] [     PegaRULES:07.10] ( UsageCleaner.Log_Usage.Action) ERROR   - Error in RDB-Delete
com.pega.pegarules.pub.database.DatabaseException: Problem encountered executing a stored procedure: code: -964 SQLState: 57011 Message: The transaction log for the database is full.. SQLCODE=-964, SQLSTATE=57011, DRIVER=4.15.113
From: (BCA6A53A5F2F8D1DE6BDBAC1CBB371BEC) 
    SQL: {call PRPC.sppr_purge_table (?,?,?)}
    SQL Inserts: <PRPC.pr_perf_stats>    <pxSnapshotTime>    <30>    

Caused by SQL Problems.
Problem #1, SQLState 57011, Error code -964: com.ibm.db2.jcc.am.SqlException: The transaction log for the database is full.. SQLCODE=-964, SQLSTATE=57011, DRIVER=4.15.113
    at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:257)
    at com.pega.pegarules.data.internal.access.SQLGenerator.callStoredProc(SQLGenerator.java:3301)
    at com.pega.pegarules.data.internal.access.DatabaseImpl.callStoredProc(DatabaseImpl.java:10110)
    at com.pega.pegarules.data.internal.access.SQLGenerator.purgeTableContainingClass(SQLGenerator.java:2871)
    at com.pega.pegarules.data.internal.access.DatabaseImpl.purgeTableContainingClass(DatabaseImpl.java:6825)
    at com.pegarules.generated.activity.ra_action_usagecleaner_ea6347a02c921b81249c7683934f6465.step5_circum0(ra_action_usagecleaner_ea6347a02c921b81249c7683934f6465.java:624)
    at com.pegarules.generated.activity.ra_action_usagecleaner_ea6347a02c921b81249c7683934f6465.perform(ra_action_usagecleaner_ea6347a02c921b81249c7683934f6465.java:147)
    at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
    at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10450)
    at com.pegarules.generated.activity.ra_action_systemcleaner_086584e6b8a1ac0ea644fcb3ea53969f.step12_circum0(ra_action_systemcleaner_086584e6b8a1ac0ea644fcb3ea53969f.java:965)
...
Caused by: 
com.ibm.db2.jcc.am.SqlException: The transaction log for the database is full.. SQLCODE=-964, SQLSTATE=57011, DRIVER=4.15.113
    at com.ibm.db2.jcc.am.fd.a(fd.java:701)
    at com.ibm.db2.jcc.am.fd.a(fd.java:60)


Steps to Reproduce



Not Applicable.


Root Cause



A defect or configuration issue in the operating environment. It seems SystemCleaner agent was disabled on the system for a long time, before it was reenabled again and this issue occurred. There were ten million records in the pr_perf_stats table, therefore when SystemCleaner agent was re-enabled, it failed as it exceeded the log file size and crashed the system.

Resolution



Make the following change to the operating environment:

Truncate pr_perf_stats table by issuing TRUNCATE SQL.

​SystemCleaner agent will now be able to process and keep the table size within limits. 

 

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

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