PEGA0005 alerts on system tables
Article SA ID: SA-22532 indicates it was written for pega alerts in 7.1.6: https://community.pega.com/support/support-articles/pega0005-alerts-alert-logs
If we are experiencing the same in 7.1.9, and have the following errors:
1) Database update took morethan the threshold of 250 ms: 7,329 ms update xxxx.pr_sys_statusnodes set pyLastPulseDateTime = ? where pzInsKey = ?
2) Database operation took morethan the threshold of 250 ms: 6,607 ms SQL: {call xxxx.sppr_sys_updatescache_gettime (?,?,?)}
Are the same indexes still valid? Or are there new indexes we need to build? The second item above is not mentioned in the original article. Are there separate indexes for that stored procedure?
Accepted Solution
Pegasystems Inc.
US
Yes - we do get errors on this table sppr_sys_reservequeueitem_b. We opened an SR for this and have resolved it. We found that the errors related to this issue were a very small percentage of the Pega0005 Alerts.
Pegasystems Inc.
IN
Hello ,
pr_sys_statusnodes table have index present on pzinskey table.
stored procedure sppr_sys_updatescache_gettime also uses the same table pr_sys_statusnodes .
Are you getting any errors on the stored procedures sppr_sys_reservequeueitem_b ,sppr_purge_table .
Please share your pega rules and alert log file to have a look .
Thanks,
Arun
Accepted Solution
Pegasystems Inc.
US
Yes - we do get errors on this table sppr_sys_reservequeueitem_b. We opened an SR for this and have resolved it. We found that the errors related to this issue were a very small percentage of the Pega0005 Alerts.