Support Article
AES 3.5 not able to show response time for split schema client
SA-3605
Summary
In AES 3.5, it is not able to pull response time data from client pr_perf_stats table only in case of split schema.
Previously pr_perf_stats table was in pegarules schema, but in split schema pr_per_stats table is in pegadata schema.
So activity excecutembean throwing exception table or view does not exist cause it still try to search in pegarules schema or pr_perf_stats table
Error Messages
No Response time graph for Monitoring AES node
Root Cause
The root cause of this problem is defect in the PRPC operating environment.
AES 3.5 not able to show response time for split schema client. Modified the Query to get the response time.
Resolution
This issue is resolved by hotfix item: HFix-10316
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.