Question
ACC3 International
US
Last activity: 15 Jul 2024 7:50 EDT
Reports Stop Responding
We have a few reports that have started to timeout with no changes being made to the reports, Pega or the database.
Now the strange part, if we change the report by deleting or adding a column (any column) the reports work again. The reports are not related in any way. The tracing shows we are waiting for the database nothing on the Pega side.
It is a Microsoft Azure SQL database. The tracer on the database side shows sp_cursorrunprepare being executed on the database.
We tried running the same SQL using RDB-List and Obj-Browse it did not work. We did it get to run using an activity calling the report definition with the paging set without adding or deleting a column.
Any ideas would be greatly appreciated. If any one knows how Pega calls the sp_cursorrunprepare sql server stored procedure that would be a great help.
Accepted Solution
Updated: 15 Jul 2024 7:50 EDT
Pegasystems Inc.
GB
Pegasystems Inc.
GB
@DavidB0382 the support team waited a month for you to respond. They have now closed the ticket as they assume your issue is now resolved.
@DavidB0382 I can see that you logged INC-B19644 in parallel and it is being investigated by our GCS engineers.
They need further details including details of any errors or warnings which you could sanitize and share. Please continue to work with them and confirm the results when your DBA flush any existing explain plans and run the erroring report again.
GCS can find no evidence of any code in Pega that would prompt the running of that stored procedure sp_cursorrunprepare and we have no references to anything Azure-MSSQL-specific in the code. cc @LONGJ
Please update this forum post once you get an analysis from the GCS staff.