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

 PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 240 posts
Anthem
Posted: Sep 20, 2018
Last activity: Nov 30, 2018
Posted: 20 Sep 2018 17:28 EDT
Last activity: 30 Nov 2018 14:44 EST
Closed
Solved

Pega Change Manager (PCM) VIOLATION dashboard issues.

Hi Team,

PCM VIOLATION dashboards are not getting displayed with the below mentioned error message.

Error:
** ** One of the join conditions involving the following unoptimized property is not allowed, since it can severely degrade performance: .pzInskey in class PCM-Work. Revise the join conditions or optimize the property.

PFA for the complete logs.

Please suggest.

***Edited by Moderator Marissa to update SR Details***

To see attachments, please log in.
Low-Code App Development
System Administration
Support Case Created

Accepted Solution

Posted: 6 years ago
Posted: 30 Nov 2018 14:41 EST
Susan Liu (SusanLiu_GCS)
PEGA
Senior Principal Engineer, Technical Support, Runtime Engine
Pegasystems Inc.
US

Hi,

The issue is in Pega’s PCM code.

 

The error comes from OOTB Report Definition "txViolationByApplication" ruleset: ECS-PCM-Server:07-20-01.
In the Report Definition, under Data Access tab, there are two class joins.
The first one has the below filter conditions:
instance.pxRefObjectkey is equal ".pzInskey". Here it should be ".pzInsKey", letter "k" should be capital.
This is a bug in product code.

Show More

Hi,

The issue is in Pega’s PCM code.

 

The error comes from OOTB Report Definition "txViolationByApplication" ruleset: ECS-PCM-Server:07-20-01.
In the Report Definition, under Data Access tab, there are two class joins.
The first one has the below filter conditions:
instance.pxRefObjectkey is equal ".pzInskey". Here it should be ".pzInsKey", letter "k" should be capital.
This is a bug in product code.

 

The local change for customer is to save the RD to their application ruleset and update it to the correct case.

 

See attached screen shot for OOTB Report Definition "txViolationByApplication".

 

 


Show Less
To see attachments, please log in.
Posted: 6 years ago
Posted: 20 Sep 2018 17:34 EDT
PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US

Hi Team,

Looks like a BUG with the pzInsKey property reference in the report definition txviolationByApplication.

Please help with the hotfix.

PFA for the Report Definition screenshot.

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 21 Sep 2018 5:47 EDT
Manjunatha Anantharaju (Manju_PEGA)
British Telecom
Senior Pega Developer
British Telecom
IN

Hi,

Can you please have a look into the below pdn links , which look similar to the issue.

https://community.pega.com/support/support-articles/we-are-seeing-exceptions-logs-complaining-about-sql-query

https://community.pega.com/support/support-articles/error-occurs-when-join-and-sub-report-use-unoptimized-property

https://collaborate.pega.com/question/class-join-works-index-class-declarative-join-doesnt

And what is the Pega version ? 

To see attachments, please log in.
Posted: 6 years ago
Posted: 24 Sep 2018 14:54 EDT
PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US

Hi Anantharaju,
PRPC version 731.

Thanks for the above provided PDN articles but they are not helpful.

It looks like a BUG with PCM.Could you please let us know the process to engage the right point of contact from PEGA.

I believe support request to GCS team might not work out.

To see attachments, please log in.
Posted: 6 years ago
Posted: 24 Sep 2018 23:49 EDT
Lochana Durgada Vijayakumar (Lochan_DV)
PEGA
Senior Manager, Knowledge Management
Pegasystems Inc.
IN

Hi Pradeep,

If you believe that this is a BUG with PCM, Support Request to GCS team is the right approach. Please create an SR with Request Type as Product Defect and mention the URL to this post. Once created, please let us know the SR# back here.

Regards,

To see attachments, please log in.
Posted: 6 years ago
Posted: 11 Oct 2018 11:36 EDT
PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US

Hi Team,
In addition to the above provided details, below mentioned error has been observed as well which might be co-related.

VIEW MONITORING NODES / CLIENTS – ON THE CLICK OF CHART ACTIONS
Error:
** ** One of the join conditions involving the following unoptimized property is not allowed, since it can severely degrade performance: AM.tyClientSystemDetails.tySystemNode in class PCM-Data-ViolatorDetails. Revise the join conditions or optimize the property.

PFA's for the screenshots.

To see attachments, please log in.
Posted: 6 years ago
Posted: 11 Oct 2018 12:10 EDT
Susan Liu (SusanLiu_GCS)
PEGA
Senior Principal Engineer, Technical Support, Runtime Engine
Pegasystems Inc.
US

HI Pradeep, 

For the 1st issue, ".pzInskey in class PCM-Work", I have discussed with SME on it. Since it is about ".pzInskey" wrong case related, you can go ahead to save the RD to your application ruleset and update it to the correct case. 

​thanks,

To see attachments, please log in.
Posted: 6 years ago
Posted: 11 Oct 2018 12:12 EDT
Susan Liu (SusanLiu_GCS)
PEGA
Senior Principal Engineer, Technical Support, Runtime Engine
Pegasystems Inc.
US

For the new issue you just posted, "AM.tyClientSystemDetails.tySystemNode in class PCM-Data-ViolatorDetails.", please wait for the response from SMEs. Thanks.

​

To see attachments, please log in.
Posted: 6 years ago
Posted: 12 Oct 2018 5:33 EDT
Swaraj Kolipaka (SwarajKolipaka)
Express Scripts

Express Scripts
US

Hi Pradeep

Regarding the issue 

VIEW MONITORING NODES / CLIENTS – ON THE CLICK OF CHART ACTIONS
Error:
** ** One of the join conditions involving the following unoptimized property is not allowed, since it can severely degrade performance: AM.tyClientSystemDetails.tySystemNode in class PCM-Data-ViolatorDetails. Revise the join conditions or optimize the property.

Property tySystemNode is already exposed in the table which is pointed by class PCM-Data-ViolatorDetails (i.e pr_pcm_data_violatordetails) under the name tysystemnode_1 and external mapping for this column has been done in class rule PCM-Data-ViolatorDetails 

Show More

Hi Pradeep

Regarding the issue 

VIEW MONITORING NODES / CLIENTS – ON THE CLICK OF CHART ACTIONS
Error:
** ** One of the join conditions involving the following unoptimized property is not allowed, since it can severely degrade performance: AM.tyClientSystemDetails.tySystemNode in class PCM-Data-ViolatorDetails. Revise the join conditions or optimize the property.

Property tySystemNode is already exposed in the table which is pointed by class PCM-Data-ViolatorDetails (i.e pr_pcm_data_violatordetails) under the name tysystemnode_1 and external mapping for this column has been done in class rule PCM-Data-ViolatorDetails 

Please check whether the column name in db and name mentioned in class rule are with same case or not.


Show Less
To see attachments, please log in.

Accepted Solution

Posted: 6 years ago
Posted: 30 Nov 2018 14:41 EST
Susan Liu (SusanLiu_GCS)
PEGA
Senior Principal Engineer, Technical Support, Runtime Engine
Pegasystems Inc.
US

Hi,

The issue is in Pega’s PCM code.

 

The error comes from OOTB Report Definition "txViolationByApplication" ruleset: ECS-PCM-Server:07-20-01.
In the Report Definition, under Data Access tab, there are two class joins.
The first one has the below filter conditions:
instance.pxRefObjectkey is equal ".pzInskey". Here it should be ".pzInsKey", letter "k" should be capital.
This is a bug in product code.

Show More

Hi,

The issue is in Pega’s PCM code.

 

The error comes from OOTB Report Definition "txViolationByApplication" ruleset: ECS-PCM-Server:07-20-01.
In the Report Definition, under Data Access tab, there are two class joins.
The first one has the below filter conditions:
instance.pxRefObjectkey is equal ".pzInskey". Here it should be ".pzInsKey", letter "k" should be capital.
This is a bug in product code.

 

The local change for customer is to save the RD to their application ruleset and update it to the correct case.

 

See attached screen shot for OOTB Report Definition "txViolationByApplication".

 

 


Show Less
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