Support Article

Unexplained exceptions in logs

SA-37698

Summary



The user is seeing exceptions in logs, and as per Pega set the TransactionIsolationLevel to 2 and it is still happening.

Error Messages



1. ERROR - Encountered an error when saving instance "LOG-RULEUSAGE 37D0A83D890ED1B00DCB36FD9E8E0E9B!COM.PEGARULES.GENERATED.HTML_SECTION.RA_STREAM_PYDELETERULEPROMPT_41EDA09E2E82E6DCEF4E9A7E3BE8CF12!RECENT" of class Log-RuleUsage
com.ibm.db2.jcc.am.SqlException: UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE 00C90088, TYPE OF RESOURCE 00000302, AND RESOURCE NAME PEGCCDBP.PGTS0100.X'00007D'. SQLCODE=-913, SQLSTATE=57033, DRIVER=3.62.57

2. ERROR - Not returning connection 1 for database "pegadata" to the pool as it previously encountered the following error
User ID: System
Last SQL: {call PEGCCDBP.sppr_purge_table (?,?,?)}
com.ibm.db2.jcc.am.SqlException: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON 00C90096, TYPE OF RESOURCE 00000302, AND RESOURCE NAME PEGCCDBP.PGTS0099.X'003C61'. SQLCODE=-904, SQLSTATE=57011, DRIVER=3.62.57


Steps to Reproduce



Run OOTB agents from multiple nodes.


Root Cause



Customer is using DB2 JDBC driver version 3.62.57.

Resolution



Upgrade to DB2 JDBC driver version 4 according to platform support guide

Published May 9, 2017 - Updated May 11, 2017


100% found this useful

Have a question? Get answers now.

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