Page tree
Skip to end of metadata
Go to start of metadata
Purpose (problem description)

This page troubleshoot the case when there is Added AETP without change in the source code:

Observed in CAST Version


Release

Yes/No

8.3.x(tick)
8.2.x(tick)
Observed in RDBMS

RDBMS

Yes/No

Oracle Server  (tick)
Microsoft SQL Server  (tick)
CSS3  (tick)
CSS2  (tick)
Action Plan

Perform the below actions

  1. Get the list of objects contributing to the ADDED automated enhancement technical point for the current snapshot by referring to SQL Queries - CAST Central Base - Queries on Objects - How to get the list of objects contributing to the ADDED automated enhancement technical point for a snapshot
    1. If the query returns rows
      1. Check if the objects contributing to the ADDED automated enhancement technical point for the current snapshot are part of the current run but not previous run, for that refer to SQL Queries - CAST Central Base - Queries on Objects - How to get the delta of objects between two snapshots, here we may encounter 3 cases:
        1. All the objects contributing to the ADDED automated enhancement technical point for the current snapshot are part of the current run but not previous run, in this case we are facing an issue of missing objects from the previous run, to investigate the issue refer to CAST Engineering Dashboard - Object - Missing objects
        2. None of the objects contributing to the ADDED automated enhancement technical point for the current snapshot are part of the current run but not previous run, in this case, the objects contributing to the ADDED automated enhancement technical point are part of the two snapshots but they are linked to only transactions of the previous snapshot. We need to get the list of objects that are part of two snapshots but they are linked to only transactions of the previous snapshot by following this page SQL Queries - CAST Central Base - Queries on Objects - How to get the list of objects that are part of two snapshots but they are linked only to transactions of the previous snapshot. Note that the natural and complementary impact of this set of objects is that you will get Modified and/or Deleted Transactions in the current snapshot on which the object involved in the Transaction has the object status itself UNCHANGED but the status in the TF is DELETED. First, Go to the Enhancement node under TCC and observe that the objects listed by the above query has the object status itself UNCHANGED but the status in the TF is DELETD, then investigate the root case as follow:
          1. Check if the object have the Role "FULL_GRAPH_OBJECT":

            If the object have the Role "FULL_GRAPH_OBJECT", then check if there is a change in the measurement mode between the snapshots from where you are observing the status variation:

            If the mode have changed from EFP mode to AEP mode or vice versa, then this is expected. In fact AEP-EFP snapshots are not comparable with each other. when you plan to change the measurement mode, it is necessary to recreate a new baseline snapshot. So, after you change the measure you must generate a new snapshot for the same Application version but it must not be considered as consistent for the new measure. The next snapshot you generate for the Application will be consistent and can be used as the first snapshot using the new enhancement measure. For more detailed explanation refer tTransitioning from EFP to AEP.
          2. If the object do not have the Role "FULL_GRAPH_OBJECT": 
            here we are probably facing an issue of "nude" object (From current run or previous run). In what follows, we will define the "nude" object, explain the reason to get a "nude object", then we will provide the methodology of identifying the "nude" object.
          3. Definition of "nude" object:
            In order to easily explain this, we take the following sample:
            Let us consider that the transaction was having the following Call graph in the previous run:

            The object "L22" will be "nude" object if the Entry point "L0" cannot reach the End point "L4" by way of the branch "L0"→ "L12"→ "L22" → "L32" → ""L4 

          4. How can this be possible?
            The path from "L0" to "L4" will be truncated by way of the branch "L0"→ "L12"→ "L22" → "L32" → ""L4, in one of the following cases:
            • Object "L12" or "L32" are deleted between the 2 runs
            • Link "L0"→ "L12" or "L12"→ "L22" or "L22"→ "L32", or  "L32"→ "L4" are deleted between the 2 runs
            • How to identify the nude object?
              1. Open TCC with current run and previous run
              2. View the full call graph of the Transaction from the current and previous run
              3. Identify The Missing path by comparing the two full call graphs
              4. If we take as an example the illustration above the call graphs will be as follows
              5. Open Enlighten with the knowledge base from where the path is missing from the call graph
              6. Try to trace the missing path:
                1. Place the object corresponding to the entry point in the Graphical View
                2. Add Linked Objects of the object corresponding to the entry point as seen in the full call graph of TCC
                3. Place the objects corresponding to the linked objects in the Graphical View
                4. Add Linked Objects of the linked objects as seen in the full call graph of TCC
                5. Do point c and d until:
                  1. You are not able to trace the Transaction because of missing link then refer to CMS Snapshot Analysis - Run Analyzer - Missing or Wrong links between two objects
                  2. Or if you are not able to trace the Transaction because of missing objects then refer to CMS Snapshot Analysis - Run Analyzer - Missing objects
                  3. Or if you are able to trace the missing path then refer to Transaction Configuration Center - AFP Calibration - Transactional Functions - Missing Links
        3. Part of the objects contributing to the ADDED automated enhancement technical point for the current snapshot are part of the current run but not previous run, and the other part of the objects contributing to the ADDED automated enhancement technical point for the current snapshot are part of the current run but not previous run, for each part proceed as above
    2. Else if the query does not returns rows then contact CAST Technical Support. with the following  Relevant input 
  2. If the above steps do not solve your issue contact CAST Technical Support. with the following  Relevant input  
Notes/comments

Ticket # Number, Number

Related Pages


  • No labels