SQL Error code: 17009 SQLState: 99999 Closed Statement DatabaseException caused by prior exception: java.sql.SQLException: Closed
Hi,
While executing RDB-List through Load-DataPage (Data page is a parameterized, its source is an activity and RDB-List was referred in this activity) method, we are getting below exception in 8.6v.
Error: ** [MSG][Error in RDB-List][STACK][com.pega.pegarules.pub.database.DatabaseException: Problem processing list results: code: 17009 SQLState: 99999 Message: Closed Statement DatabaseException caused by prior exception: java.sql.SQLException: Closed Statement | SQL Code: 17009 | SQL State: 99999
Few more details from tracer:
Caused by SQL Problems. Problem #1, SQLState 99999, Error code 17009: java.sql.SQLException: Closed Statement at com.pega.pegarules.data.internal.access.ExceptionInformation.createAppropriateExceptionDueToDBFailure(ExceptionInformation.java:385) at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:364) at com.pega.pegarules.data.internal.access.RDBPageResultPackager.packageDataStoreResults(RDBPageResultPackager.java:439) at....
Is there any way we can resolve this?
Note: When I execute the SQL query (formed dynamically), it is not having any issues. I am able to see correct results.
Is this issue happening due to DB connection? The connection was successfully established at some point, but when RDB-List tried to execute right there, the connection was no longer open?
Pegasystems Inc.
GB
@srinit what does the activity actually do?
Which user is running the large query against the database? Are the relevant indexes and schema permissions in place for the Pega external DB side for the RDB-List use?
If this needs looking at in more depth I would suggest that you log a support incident on the MSP . In the ticket please provide the full debug pegaRULES and PegaALERT logs and Tracer, illustrating your pega test and the SQL query test methods used.
You can use the DB Trace feature of the Performance tool to view in depth the SQL operations of a Connect SQL rule.
Execution of this method may cause an alert to be added to the Alert log, of type PEGA004 - PEGA007, PEGA0025, or PEGA0028. Review the Alert log to understand the frequency and sources of such alerts, and for best performance, alter your application or database to eliminate those alerts that occur frequently.
You can use the DB Trace feature of the Performance tool to view in depth the SQL operations of a Connect SQL rule.
Please let us know the INC reference if you chose to log a support incident.