Report definition error - caught exception during autocommit check
Hi All,
I am trying to run a report definition using Action--> Run. When I ran it first time it gave me an error "Error:** Retrieving the report data exceeded the limit of '30' seconds. Please try making the report more specific by further limiting which rows to include." Then i reset the maximum time elapsed. when i run the report definition again i got the following error. "Error:** An error occured on executing the query for the report definition - caught exception during autocommit check".
Database used: postgre
"Release_ViolationsList" is the report definition i tried to run. When i checked the pega logm, i found the following. (please refer the attachement)
Could you please help me on this
Thanks and Regards
Riyaz
***Updated by moderator: Lochan to add Categories***
Accepted Solution
OCBC Bank
MY
Hi,
The issue is due to huge data. In my case i limited the amount of data it tries to retriew. Thank you for the support given.
Thanks and Regards
Riyaz
BUPA
AU
Hi Riyaz,
Did you try to run the SQL in Postgres and checked the result?
Hi Riyaz,
Did you try to run the SQL in Postgres and checked the result?
SELECT "PC0"."updatedatetime" AS "UpdateDateTime" , "PC0"."rulename" AS "RuleName" , "Warning"."type" AS "Type" , "Warning"."severity" AS "Severity" , "Warning"."name" AS "Name" , "Warning"."message" AS "Message" , "PC0"."rulereference" AS "RuleReference" , "Warning"."status" AS "Status" , "Op"."pyusername" AS "pyUserName" , "Op"."pyimagefilename" AS "pyImageFileName" , "PC0"."ruleset" AS "RuleSet" , "PC0"."rulesetversion" AS "RuleSetVersion" , "Team"."name" AS "Name" , "Warning"."historyreference" AS "HistoryReference" , "Warning"."repeatingindex" AS "RepeatingIndex" , "Warning"."justifiedmeassage" AS "JustifiedMeassage" , "Jop"."pyusername" AS "pyUserName" , "Jop"."pyimagefilename" AS "pyImageFileName" , "PC0"."ruletype" AS "RuleType" FROM pegadata.vrtu_era_rulechange "PC0" INNER JOIN pegadata.vrtu_era_warning "Warning" ON ( ( "PC0"."historyreference" = "Warning"."historyreference" AND "Warning"."operation" = ? ) ) INNER JOIN pegadata.pr_operators "Op" ON ( ( "PC0"."updateoperator" = "Op"."pyuseridentifier" ) AND "Op"."pxobjclass" = ? ) LEFT OUTER JOIN pegadata.vrtu_era_team "Team" ON ( ( "PC0"."team" = "Team"."teamid" ) ) LEFT OUTER JOIN pegadata.pr_operators "Jop" ON ( ( "Warning"."justifyoperator" = "Jop"."pyuseridentifier" ) AND "Jop"."pxobjclass" = ? ) WHERE ( "PC0"."release" = ? ) ORDER BY 1 DESC
Pls add some index in the tables to make it faster so that Pega can execute and get the result within threshold limit.
Accepted Solution
OCBC Bank
MY
Hi,
The issue is due to huge data. In my case i limited the amount of data it tries to retriew. Thank you for the support given.
Thanks and Regards
Riyaz