Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

AES overview: top offenders page does not display response times

SA-2073

Summary



In the AES overview of the top offenders, response times in the projected average response time savings is not displayed. It does not reflect the response times in the overview and listings. It does not seem to be calculated or recorded.


Error Messages



When performing a trace (of Open the AES manager portal) the following is displayed:


There was a problem getting a list: code: 936 SQLState: 42000 Message: ORA-00936: missing expression

Steps to Reproduce



Open the AES manager portal.



Root Cause



The root cause of this problem is defect or misconfiguration in the PRPC operating environment.

The AES system is retrieving data from pegaam_perf_stats table to generate the Report in Top Offenders page in AES console. Executing the below SQL query on the problem system, indicated there has been no data inserted to the table since 15-Dec-13

select * from pegaam_perf_stats p where rownum <=100 order by p.pxsnapshottime desc; 

The AESPROCESSNIGHTLYTASKS Agent executes 1:00 am daily to pull data from the monitored node and then inserting the data into pegaam_perf_stats table. When running the Agent Activity RULE-OBJ-ACTIVITY PEGAAES- AESPROCESSNIGHTLYTASKS with DBTracer enabled, the following SQL statement should be executed, but this is not happening on the problem system.

insert into pegaam_perf_stats
(AVERAGEASSEMBLYCOUNT , AVERAGECOMPILATIONCOUNT , AVERAGECPUTIME ,
AVERAGERESPTIME , CLUSTERNAME , GDT_DAY , GDT_HOUR , GDT_MONTH ,
GDT_YEAR , PXACTIVITYCOUNT , PXALERTCOUNT , PXCOMMITELAPSED ,
PXCONNECTCOUNT , PXCONNECTELAPSED , PXDBINPUTBYTES , PXDBOUTPUTBYTES ,
PXDECLARATIVERULESINVOKEDCOUNT , PXFLOWCOUNT , PXINPUTBYTES , PXINSNAME ,
PXINTERACTIONS , PXJAVAASSEMBLECOUNT , PXJAVACOMPILECOUNT , PXOBJCLASS ,
PXOTHERBROWSEELAPSED , PXOTHERBROWSERETURNED , PXOTHERIOCOUNT , PXOTHERIOELAPSED ,
PXOUTPUTBYTES , PXPROCESSCPU , PXREQUESTORTYPE , PXRULEBROWSEELAPSED , PXRULEBROWSERETURNED ,
PXRULECOUNT , PXRULEIOELAPSED , PXSERVICECOUNT , PXSNAPSHOTTIME , PXSNAPSHOTTYPE ,
PXSYSTEMNAME , PXSYSTEMNODE , PXSYSTEMNODEID , PXTOTALREQCPU , PXTOTALREQTIME ,
UNIQUEREQUESTORS , UNIQUEUSERS , pzInsKey) values (? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ? , ?)  <0.0> <0.0> <0.39626666666666666> <0.843> <PRPC62SP1_NODE_AES> <1> <23> <9> <2014> <236> <5> <0.209> <53> <1.141> <11008522> <82472> <15> <1> <2465> <BROWSER!1051911DDDE0A526686ADFC29BFF338F!20140901T230000.000 GMT!DAILY> <15> <0> <0> <PegaAES-Data-LogUsage> <0.011> <2> <745> <3.687> <708436> <228.479> <BROWSER> <0> <0> <85> <0.449> <0> <2014-09-02 00:00:00.0> <DAILY> <PRPC62SP1_NODE_AES> <wchans3w7> <1051911ddde0a526686adfc29bff338f> <5.944> <12.645> <1> <1> <PEGAAES-DATA-LOGUSAGE BROWSER!1051911DDDE0A526686ADFC29BFF338F!20140901T230000.000 GMT!DAILY>

update pegaam_perf_stats set AVERAGEASSEMBLYCOUNT = ? , AVERAGECOMPILATIONCOUNT = ? , AVERAGECPUTIME = ? , AVERAGERESPTIME = ? , CLUSTERNAME = ? , GDT_DAY = ? , GDT_HOUR = ? , GDT_MONTH = ? , GDT_YEAR = ? , PXACTIVITYCOUNT = ? , PXALERTCOUNT = ? , PXCOMMITELAPSED = ? , PXCONNECTCOUNT = ? , PXCONNECTELAPSED = ? , PXDBINPUTBYTES = ? , PXDBOUTPUTBYTES = ? , PXDECLARATIVERULESINVOKEDCOUNT = ? , PXFLOWCOUNT = ? , PXINPUTBYTES = ? , PXINSNAME = ? , PXINTERACTIONS = ? , PXJAVAASSEMBLECOUNT = ? , PXJAVACOMPILECOUNT = ? , PXOBJCLASS = ? , PXOTHERBROWSEELAPSED = ? , PXOTHERBROWSERETURNED = ? , PXOTHERIOCOUNT = ? , PXOTHERIOELAPSED = ? , PXOUTPUTBYTES = ? , PXPROCESSCPU = ? , PXREQUESTORTYPE = ? , PXRULEBROWSEELAPSED = ? , PXRULEBROWSERETURNED = ? , PXRULECOUNT = ? , PXRULEIOELAPSED = ? , PXSERVICECOUNT = ? , PXSNAPSHOTTIME = ? , PXSNAPSHOTTYPE = ? , PXSYSTEMNAME = ? , PXSYSTEMNODE = ? , PXSYSTEMNODEID = ? , PXTOTALREQCPU = ? , PXTOTALREQTIME = ? , UNIQUEREQUESTORS = ? , UNIQUEUSERS = ? where pzInsKey = ?  <0.0> <0.0> <0.39626666666666666> <0.843> <PRPC62SP1_NODE_AES> <1> <23> <9> <2014> <236> <5> <0.209> <53> <1.141> <11008522> <82472> <15> <1> <2465> <BROWSER!1051911DDDE0A526686ADFC29BFF338F!20140901T230000.000 GMT!DAILY> <15> <0> <0> <PegaAES-Data-LogUsage> <0.011> <2> <745> <3.687> <708436> <228.479> <BROWSER> <0> <0> <85> <0.449> <0> <2014-09-02 00:00:00.0> <DAILY> <PRPC62SP1_NODE_AES> <wchans3w7> <1051911ddde0a526686adfc29bff338f> <5.944> <12.645> <1> <1> <PEGAAES-DATA-LOGUSAGE BROWSER!1051911DDDE0A526686ADFC29BFF338F!20140901T230000.000 GMT!DAILY>

Performing a trace when running the AESPROCESSNIGHTLYTASKS activity manually displays that RULE-OBJ-ACTIVITY PEGAAES-DATA-CLUSTER COLLECTLOGUSAGEDATADAILYCLUSTER terminated at step 4. Looking into the logic of this activity, the termination occurs because the cluster in the problem system was not enabled.

When looking into the cluster setting of Class Explorer > PegaAES > Data > Cluster in the problem system, the enabled flag was not set. When attempting to open the cluster node rules, the rule forms never open successfully which suggested the cluster is incorrect or possibly corrupt.



Resolution



This issue was resolved through the following local-change to recreate the AES Managed Cluster.

Initially, remove the existing Cluster in the AES Manager console > Administration. Under the Manage Cluster section, the remove cluster option is available.

Follow the appropriate documentation to recreate the cluster as per the information provided on the PDN for AES.
https://pdn.pega.com/products/autonomic-event-services-enterprise-edition

 
Suggest Edit

Published January 31, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us