Support Article
Frequent ORA-01013 errors after Pega 7.1.7 update
SA-3592
Summary
Frequent "ORA-01013: user requested cancel of current operation" errors after updating to Pega 7.1.7.
This often happens during expanding a tree in App Explorer, but it seems to also happen independently.
Application server is JBoss 6.1.1, Database Oracle 11g 11.2.0.4 (jdbc driver ojdbc6.jar 11.2.0.4)
Error Messages
16:27:30,080 INFO [stdout] (Dispatcher-Thread-76) 2014-11-18 16:27:30,060 [ AsyncServices-5] [ STANDARD] [ ] [ FW:01.01.01] ( rd.queryexec.SqlQueryExecutor) ERROR pega |127.0.0.1 XXXXX - 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
16:27:30,080 INFO [stdout] (Dispatcher-Thread-76)
16:27:30,080 INFO [stdout] (Dispatcher-Thread-76) com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: 1013 SQLState: 72000 Message: ORA-01013: user requested cancel of current operation
Steps to Reproduce
Sometimes happens when expanding tree in App Explorer, but might be unrelated to that specific operation. I was not able to consistently reproduce it, but it also seems that there are some moments where expanding the tree is much slower than before. It also seem to only happen when somebody is working with the application - it does not show up during night and is always associated with user.
Root Cause
The root cause of this problem is defect/misconfiguration in the database. The indexes where missing after the upgrade.
Resolution
This issue is resolved through the following local change: Stored procedure SPPR_REBUILD_INDEXES was used to rebuild database indexes and solved the issue.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.