Support Article
Pega application freezes in prod env post app server upgrade
SA-2107
Summary
After upgrading WebSphere application server from version 6.1 to 7 with no application code changes, user noticed many very long running queries in the alert logs for a stored proc call used for processing SLA's per PDN documentation.
User has not noticed these long running queries in the past and not sure about the cause.
User requested Pega Support Personnel to review the Pega code and alert logs for possible causes.
Error Messages
Database operation took more than the threshold of 5000 ms: 599,812 ms SQL: {call sppr_sys_reservequeueitem_b ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) }
Steps to Reproduce
Not Applicable.
Root Cause
The root cause of this problem is defect or misconfiguration in the PRPC operating environment.
Specifically, the following index was not added as part of the 5.5 to 6.2SP2 upgrade:
CREATE INDEX pr_sys_queue_sla_index1 ON pr_sys_queue_sla (pyMinimumDateTimeForProcessing ASC, pzInsKey ASC, pyItemStatus ASC, pyAgentName ASC);
Resolution
This issue is resolved through the following local-change:
Add above mentioned index and suggest to review the PRPC 6.2 SP2 media and the Oracle upgrade scripts.
Ensure that all the index updates are implemented. (upgrade0505SP1to62SP2 directory in the upgrade media)
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.