Posted: 20 Jun 2019 13:47 EDT Last activity: 27 Mar 2020 10:19 EDT
BIX issue in production
We are observing below error in production. attached complete bix log.
Unable to process Data-Decision-IH-Fact: PRRuntimeException
Caused by: com.pega.pegarules.data.internal.rd.queryexec.ExecuteQueryException: An error occured on executing the query for the report definition - There was a problem getting a list: code: 1013 SQLState: 72000 Message: ORA-01013: user requested cancel of current operation
DatabaseException caused by prior exception: java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation
we have not cancelled any operation in bix for this. can somebody help me in understanding what could have went wrong here?
***Edited by Moderator Marissa to update platform capability tags****
This looks like the query is timing out. What version of Pega/BIX are you running? It probably would be useful to see the full PegaBIX log but can you just look and see if the timeout error is happening after 30 seconds.
Posted: 2 years ago
Posted: 22 Jun 2019 1:42 EDT
Abhinav Gupta (Abhinav7)
Principal Technical Solutions Engineer
Data-Decision-IH-Fact class is linked with PR_DATA_IH_FACT table in database.It contains transactional data that may grow fast.Can you verify size of this table.I suspect it has lot of records and while processing them query is being timed out.
If you do not need all the data then you can archive older data.Please follow below link for more details.
Caused by: com.pega.pegarules.data.internal.rd.queryexec.ExecuteQueryException: An error occured on executing the query for the report definition - There was a problem getting a list: code: 1013 SQLState: 72000 Message: ORA-01013: user requested cancel of current operation -
The above error says the query generated by BIX is taking more than 30 Sec. to fetch the data.
Either you need to add the DSS "BIX/selectQueryTimeout" on "Pega-Rules" and set its value to the time more than the query execution time in secondsand restart the server or use "Extract since last run" option so that only new records will get extracted or tune the query/ add more filter condition to fetch less data so that the query execution can be completed within 30 Sec.