Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation - Transaction status is UNCHANGED with transaction objects status is not UNCHANGED

Description

This page troubleshoots the issue of Transaction appearing as Unchanged even though the objects of the transaction appear as ADDED, DELETED or MODIFIED.

Figure 1

Observed in CAST AIP

Observed on RDBMS

Step by Step Scenario

Below is the step-by-step scenario leading to the problem

1. Take at least 2 snapshots
2. Open TCC
3. Go to evolution node
4. Select one Transaction
5. Observe the issue

Action Plan

1. Check if the UNCHANGED object is part of the Transaction but not part of the snapshot, for this refer to SQL Queries - CAST Central Base - Corruptions on Transactions - How to list and clean the objects that are part of Transaction but not part of snapshot . If yes then refer to the same page to clean the corruption.
   You may also check if you have the same corruption for Data Functions by referring to the following page SQL Queries - CAST Central Base - Corruptions on Data Function - How to list and clean Data Functions that are targeting the same Object, if yes then you can clean this corruption.

   Note that this issue is fixed since CAST AIP 8.1.5

2. Check if the UNCHANGED objcet is not Excluded, note that the purpose of this functionality is to prevent certain modified objects from causing a modified transaction (somehow we may decide that the modifications of certain objects must not impact the global status of the transaction, and thus we exclude it). You can check this easlly from TCC GUI:
   Figure 2

3. If the above steps do not resolve your issue, then contact CAST Technical Support with the following Relevant input

Notes/comments

Ticket # 8255