CAST Engineering Dashboard - Quality rule - Duplicate Quality Rules - Duplicated quality rules in FRAME_PORTAL_INVESTIGATION_VIEW

Description

This page handle the issue when you get duplicated quality rules and duplicated technical criteria on one of the CED views, as example this can be observed in the FRAME_PORTAL_INVESTIGATION_VIEW - Investigation - Quality Model Drilldown (Please refer to the following page for more information about this view FRAME_PORTAL_INVESTIGATION_VIEW - Investigation - Quality Model Drilldown)

Observed in CAST AIP

Observed on RDBMS

Step by Step scenario

1. Run analysis and take snapshot

Action Plan

1. Check if the duplication comes from the table metric_histo_tree, the go to the next step
2. If the duplication comes from the table metric_histo_tree, then this is due to a corruption in the Dashboard service, in order to fix this please refer to Perform the remediation ofduplication on the table metric_histo_tree

If this don’t solve your issue, then please contact CAST Technical Support and provide the relevant input

Relevant input

1. Sherlock export with the following options: Export Logs (feature checked by default), Export Configuration files (feature checked by default), Export Computer Environment (feature checked by default),Export CAST Bases

duplication comes from the table metric_histo_tree

Duplication comes from the table metric_histo_tree

SELECT snapshot_id, 
       metric_parent_id, 
       metric_id, 
       metric_index, 
       metric_type, 
       aggregate_weight, 
       metric_critical, 
       Count(1) 
FROM   dss_metric_histo_tree dmht 
GROUP  BY snapshot_id, 
          metric_parent_id, 
          metric_id, 
          metric_index, 
          metric_type, 
          aggregate_weight, 
          metric_critical 
HAVING Count(1) > 1 
ORDER  BY snapshot_id, 
          metric_parent_id, 
          metric_id, 
          metric_index, 
          metric_type, 
          aggregate_weight, 
          metric_critical

Query example:

53;550;551;1;2;1;0;2
53;552;553;1;2;1;0;2
53;554;555;1;2;1;0;2
53;556;557;1;2;1;0;2
53;558;559;1;2;1;0;2

In the above example, we can see that the last column returns 2, which is not expected, the value should not exceed 1. If it’s your case then please perform the next step in the action plan

Delete duplication

Perform the remediation of duplication on the table metric_histo_tree

This issue is due to a corruption in the Dashboard service, in order to fix this please perform the following:

1. Make a backup of the Dashboard service

2. Run the following queries on the central schema:

update DSS_METRIC_TYPE_TREES set metric_id = - metric_id;

   ```sql
INSERT INTO dss_metric_type_trees 
            (metric_parent_id, 
             metric_id, 
             metric_index, 
             aggregate_weight, 
             metric_scope_procedure_name, 
             metric_scope_procedure_name_2, 
             metric_critical) 
SELECT DISTINCT metric_parent_id, 
                -metric_id, 
                metric_index, 
                aggregate_weight, 
                metric_scope_procedure_name, 
                metric_scope_procedure_name_2, 
                metric_critical 
FROM   dss_metric_type_trees;

delete from DSS_METRIC_TYPE_TREES
where METRIC_ID < 0;

3. Run snapshot by skipping analysis

Notes/comments

Ticket # 7780

Related Pages