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

 Divya B (DivyaB)
conneqt business solutions
Divya B
conneqt business solutions
IN
DivyaB Member since 2019 7 posts
conneqt business solutions
Posted: May 10, 2023
Last activity: Aug 7, 2023
Posted: 10 May 2023 7:06 EDT
Last activity: 7 Aug 2023 10:32 EDT
Closed

Pega cache tables

Hi All,

We are upgrading Pega from 7.2.2 to 8.7,we would like to know what are all cache tables can be ignored while moving data from 7.2.2 to 8.7?  So it can improve the performance.

 

I got below tables when I googled, can we consider same tables for now as well?

pr_sys_app_hierarchy_flat;

pr_sys_app_ruleset_index;

pr_sys_class_ancestors;

pr_assembledclasses;

pr4_rule_sysgen;

pr_sys_appcache_entry;

pr_sys_appcache_dep;

pr_sys_appcache_shortcut;

pr_sys_cache_dep;

pr_sys_cache_entry;

pr_sys_cache_impl;

pr_sys_cache_dep;

Thanks

Divya

 

To see attachments, please log in.
Pega Platform 7.2.2
System Administration
Installation and Deployment
Updates
Senior System Architect

Posted: 1 year ago
Updated: 1 year ago
Posted: 10 May 2023 13:24 EDT
Updated: 10 May 2023 13:25 EDT
Guthula Bhargav prakash (Bhargav Prakash)
wipro
Guthula Bhargav prakash
wipro
IN

Hi @DivyaB,

Here are some of the cache tables that can be safely ignored while migrating to 8.7:

  1. pr4_rule_vw - This table stores the rule cache for various rule types. It can be ignored during the migration as the cache will be rebuilt after the upgrade is complete.

  2. pr_sys_appcache - This table stores the application cache data. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  3. pr_sys_app_cache_dep - This table stores the dependencies for the application cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  4. pr_sys_app_cache_vw - This table stores the versioned data for the application cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  5. pr_sys_cache_dep - This table stores the dependencies for the system cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  6. pr_sys_cache_impl - This table stores the implementation details for the system cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  7. pr_sys_cache_vw - This table stores the versioned data for the system cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

Show More

Hi @DivyaB,

Here are some of the cache tables that can be safely ignored while migrating to 8.7:

  1. pr4_rule_vw - This table stores the rule cache for various rule types. It can be ignored during the migration as the cache will be rebuilt after the upgrade is complete.

  2. pr_sys_appcache - This table stores the application cache data. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  3. pr_sys_app_cache_dep - This table stores the dependencies for the application cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  4. pr_sys_app_cache_vw - This table stores the versioned data for the application cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  5. pr_sys_cache_dep - This table stores the dependencies for the system cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  6. pr_sys_cache_impl - This table stores the implementation details for the system cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

  7. pr_sys_cache_vw - This table stores the versioned data for the system cache. You can ignore this table during migration as the cache will be rebuilt after the upgrade is complete.

It is important to note that ignoring these cache tables during migration can help improve performance as the cache will be rebuilt automatically after the upgrade is complete.It is always recommended to take a backup of these tables before making any changes.

Thanks,

Bhargav

Show Less
To see attachments, please log in.
Posted: 1 year ago
Updated: 1 year ago
Posted: 11 May 2023 2:52 EDT
Updated: 11 May 2023 2:53 EDT
Saikishore Sanagapalli (Kishore Sanagapalli)
LTIMindtree
Senior Specialist - Pega Containerization Practitioner
LTIMindtree
SA

@DivyaB

Truncating the below Tables during the Upgrades, Re-Installations will give you better performance.

 

Truncate table <DATA-Schema>.pr_sys_delayed_queue;

Truncate table <DATA-Schema>.pr_data_stream_nodes;

Truncate table <DATA-Schema>.pr_data_stream_sessions;

Truncate table <DATA-Schema>.pr_sys_statusnodes;

Truncate table <DATA-Schema>.pr_sys_statusdetails;

Truncate table <DATA-Schema>.pr_data_stream_node_updates;

TRUNCATE table <DATA-Schema>.pr_perf_stats;

Perform the Truncation steps for below DB Tables when the Indexes are not visible in the Pega Application UI.

Truncate table <DATA-Schema>.PR_SYS_QUEUE_FTSINDEXER;

Truncate table <DATA-Schema>.pr_log_cluster;

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