Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Sudhanshu Singh (SudhanshuS5799) Capgemini
Capgemini
ES
SudhanshuS5799 Member since 2014 4 posts
Capgemini
Posted: May 13, 2016
Last activity: Apr 6, 2018
Posted: 13 May 2016 9:08 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

DB issue after upgrading to Pega 7.2

A long query of approx 5500 lines is running on pr_index_reference table after upgrade which makes the server very slow.

What could be the reason?



**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 8 years ago
Posted: 22 Jun 2016 2:45 EDT
Dhevendra Earva (earvd) PEGA Senior Director of Cloud Engineering
Pegasystems Inc.
IN

Did you run the rebuild indexes stored procedure after the upgrade?. This is one of the root cause for slow running query.

 

To see attachments, please log in.
Posted: 8 years ago
Updated: 8 years ago
Posted: 23 Jun 2016 4:48 EDT
Updated: 23 Jun 2016 4:49 EDT
Vigneshwaran Aravindhan (VigneshAravind) Cognizant Senior Technology Architect
Cognizant
IN

Run RULES_SCHEMA.SPPR_REBUILD_INDEXES to rebuild the indexes.

After this verify the PegaAlertLogs for any alerts from pr_index_reference table.

Please let us know if this helped.

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice