ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Error 500 when filtering on portlets / portlet hangs due to DB issue
Article ID: 198639
Updated On:
Products
Clarity PPM SaaS
Clarity PPM On Premise
Issue/Introduction
Post migration to GCP/Postgres, we see issues with multiple custom Timesheet portlets where they hang (slow performance) or we get error 500 when filtering.
Cause
This can be due to a Database (DB) issue including stale statistics on tables used by the portlet (PRTIMEENTRY, PRTIMESHEET & PRASSIGNMENT tables)
Environment
Release : All Supported Releases
Component : CA PPM SAAS STUDIO
Resolution
On Premise customers:
- Have the DBA gather stats manually on the impacted tables which should correct the issue
SaaS customers:
- Please contact Broadcom support for assistance
Note: See the additional information section for other known causes as well.
Additional Information
- See also Slow Portlet Performance for NSQL portlets using multi-select filtering due to a defect fixed in 15.8.1.1 and higher.
- See Portlet errors/hangs when filtering on large data in GCP/Postgres - due to issue with design of portlet Query
Feedback
Yes
No
Powered by
