Support Article
Database Exception error log for Log Usage stats
SA-20353
Summary
During standard operations, exceptions are generated in the PegaRULES log file.
Error Messages
SQL: MERGE INTO your_dataschema.pr_log_reportstats t USING (VALUES (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?
, ? , ?)) AS inputs ("pzInsKey" , "pxCreateDateTime" , "pxCreateSystemID" , "pxErrorCount" , "pxInsName" ,
"pxModeOfExecution" , "pxObjClass" , "pxReportExecutionCount" , "pxReportInsKey" , "pxReportOperator" , "pxRowsRetrieved"
, "pxSaveDateTime" , "pxSessionId" , "pxTotalElapsedTime" , "pyClassName" , "pyStreamName") ON (t.pzInsKey =
inputs."pzInsKey") WHEN MATCHED THEN UPDATE SET PXCREATEDATETIME = inputs."pxCreateDateTime" , PXCREATESYSTEMID =
Steps to Reproduce
Unknown
Root Cause
A defect in Pegasystems’ code or rules:
During normal processing done by the SystemCleaner agent, some data removed had expired.
This process executes this command prior to deleting the expired rows.
'ALTER TABLE ' || tablename || ' activate not logged initially';
If the subsequent delete statement fails during the purge of the table and there there is an attempt to rollback the changes, then the table is left in an inconsistent state and the above error is generated for any subsequent DML request. DB2 requires that action to address the problem table.
Resolution
Perform the following local-change:
- Refer to IBM DB2 documentation regarding SQLState 55019, Error code -1477:
- Drop the table your_dataschema.pr_log_reportstats and recreate the table.
- Consult the database administrator regarding this action.
Published November 3, 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.