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.

Question

 Tanul Thanvi (Tanul_Thanvi)
Coforge

Coforge
GB
Tanul_Thanvi Member since 2022 4 posts
Coforge
Posted: Nov 21, 2022
Last activity: Dec 13, 2022
Posted: 21 Nov 2022 11:03 EST
Last activity: 13 Dec 2022 7:48 EST
Closed
Solved

Clearing pr_sys_ruleset_index and pr_index_reference

HI Team, we are running an out of place upgrade and first step is to migrate rules schema. Seems all the rest of tables get done within  an hour but the two tables pr_sys_ruleset_index and pr_index_reference are taking more than 4 hours - they contain 23M+ and 3M+ records respectively

question: Can we simply truncate them before migration to reduce the migrate time. We can use prpcUtils to regenerate index reference table. Will running an upgrade on a ruleschema without these two tables work ok?

To see attachments, please log in.
Pega Platform
Updates
Installation and Deployment
Insurance

Posted: 1 year ago
Posted: 13 Dec 2022 7:48 EST
Saikishore Sanagapalli (Kishore Sanagapalli)
LTIMindtree
Senior Specialist - Pega Containerization Practitioner
LTIMindtree
SA

@Tanul_Thanvi

FYI: It's of No harm in performing Truncation about the Tables you have mentioned. Since those Tables are not the actual System Cache Tables, it'll not be specified on purpose usually. Otheriwse no issue in Truncating the them.

 

To see attachments, please log in.

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