Posted: 19 Jan 2017 18:58 EST Last activity: 21 Jan 2017 18:07 EST
Pega server is responding slowly. Log files are throwing below error:
"pyClass;java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation;; at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450); at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399); at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017); at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655); at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:249); at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:566); at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:215); at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:58); at "
***Updated by moderator: Lochan to add Categories***
The error "ORA-01013: user requested cancel of current operation" is an "information" error from Oracle indicating that the current operation has been cancelled. This error will be generated if the user cancels the current operation or in response to other errors such as timeouts.
Please check the following
1) Whether your entire application is slow or only for some use case?
2) Verify alert log to nail down the queries causing the issue.
3) Involve your DBA to verify all the indexes are proper if not rebuild the same (perform gather stats).
4) If your DB is oracle, Involve your DBA to verify the AWR report which will give the list of queries causing the issue and take necessary tuning mechanism.
In addition to othos' comment, i would first find out the timestamp when the above error occurred. Then refer to same time in the alert log and look for PEGA0005 to identifiy the long running query and the corresponding activity.