Support Article
NBAM Portal Slow to display or refresh
SA-16944
Summary
In somne environments, the NBAM Portal is taking minutes to display.
User Environment Details:
- Pega 7.1.5
- NBAM 7.11
Error Messages
PEGA0005 Alert shown the following query as source of the problem:
SELECT "PC0".PYID AS "pyID",
"PC0".PYACTION AS "pyAction",
"PC0".PYRULENAME AS "pyRuleName",
"PC0".PXCREATEOPNAME AS "pxCreateOpName",
"PC0".PXOBJCLASS AS "pxObjClass",
"PC0".PXUPDATEDATETIME AS "pxUpdateDateTime",
"PC0".PYORIGUSERID AS "pyOrigUserID",
"PC0".PYCREATEDBY AS "pyCreatedBy",
"PC0".PYRULESET AS "pyRuleSet",
"PC0".PYRULESETVERSION AS "pyRuleSetVersion",
"PC0".PYRULEINSNAME AS "pyRuleInsName",
"PC0".PYRULEOBJCLASS AS "pyRuleObjClass",
"PC0".PYRULETYPE AS "pyRuleType",
"PC0".PYTEXT AS "pyText",
"PC0".PYRULECLASSNAME AS "pyRuleClassName",
"PC0".PYSOURCEID AS "pySourceID",
"PC0".PYSOURCEKEY AS "pySourceKey",
"PC0".PYDESCRIPTION AS "pyDescription",
DATA.pr_read_from_stream('.WorkName', "PC0".pzInsKey, "PC0".pzPVStream) AS "WorkName",
DATA.pr_read_from_stream('.WorkType', "PC0".pzInsKey, "PC0".pzPVStream) AS "WorkType",
DATA.pr_read_from_stream('.WorkClass', "PC0".pzInsKey, "PC0".pzPVStream) AS "WorkClass",
DATA.pr_read_from_stream('.WorkHandle', "PC0".pzInsKey, "PC0".pzPVStream) AS "WorkHandle",
"PC0".PZINSKEY AS "pzInsKey"
FROM DATA.pc_events "PC0"
INNER JOIN RULES.pr_sys_ruleset_index "SRI" ON (((("PC0".PYRULESET = "SRI".PZRULESETNAME)
AND (("PC0".PZRULESETVERSIONMAJOR = "SRI".PZRULESETVERSIONMAJOR)
OR ("PC0".PZRULESETVERSIONMAJOR = ?))
AND ("SRI".PZRULESETLISTHASH = ?))
AND ("PC0".PXOBJCLASS LIKE ?)
AND ("SRI".PXOBJCLASS = ?)))
WHERE ((("PC0".PZRULESETVERSIONMINOR <= "SRI".PZRULESETVERSIONMINOR)
OR ("SRI".PZRULESETVERSIONMINOR = ?))
AND (("PC0".PZRULESETVERSIONPATCH <= "SRI".PZRULESETVERSIONPATCH)
OR ("SRI".PZRULESETVERSIONPATCH = ?))
AND ("PC0".PXCREATEOPNAME != ?)
AND ((("PC0".PYRULENAME NOT LIKE ? ESCAPE '/')
AND ("PC0".PYRULENAME NOT LIKE ? ESCAPE '/')
AND ("PC0".PYRULENAME NOT LIKE ? ESCAPE '/'))
OR ("PC0".PYRULENAME IS NULL)))
ORDER BY 6 DESC, 1 DESC
Steps to Reproduce
Display or refresh the Next Best Action Studio portal.
Root Cause
A defect or configuration issue in the operating environment: PEGA00005 alerts found in the logs shown performance issue related to Report Definition Pega-Event.pzEventsReportDefinition. The report pzEventsReportDefinition is taking too long to execute due to the large amount of data contained in table PC_EVENTS. This report is used to retrieve the data presented in the pyeventfeedgadget section included on the Next Best Action Marketing Portal Landing Page.
Resolution
Perform the following local-change:
The following support article: https://pdn.pega.com/node/329786 provide details about the table PC_EVENTS:
“The PC_EVENTS table is a news feed table for business events information occurring within the PRPC instance.
Items are created either by Complex Event Processing or Rule saves; other business process may add instances to this table.
This table supports the Designer Studio’s What’s Happening display, RSS feed and the Recent Actions gadget.”
As recommended in the support article the table PC_EVENTS can be safely truncated after taking a backup.
This will speed up the report execution time and the landing page load.
The relative section obviously will be shown empty
Tags:
Published January 31, 2016 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.