Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation on Documentation - V2

Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation - Transactions status are ADDED and DELETED

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page troubleshoot the case when you get Transactions that have the status ADDED and the status DELETED:

Figure 1

Observed in CAST AIP

Release	Yes/No
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS2	✅
CSS1	✅

Action Plan

Check if the behavior is due to the following corruption SQL Queries - CAST Central Base - Corruptions on Transactions - How to list and clean Transactions that are targeting the same Object. If yes then apply the steps that cleanup this corruption then perform the bellow sub steps, else go to the next step :

Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation - Transaction status is ADDED with unchanged source code

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page explains the case when the transaction is flagged as modified in the evolution node, while there is no change in the analyzed code source.

Observed in CAST AIP

Release	Yes/No
8.2.x	✅
8.1.x	✅
8.0.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS2	✅

Step by Step scenario

Run at least 2 snapsots
Connect to TCC
Observe the variation

Action Plan

Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation - Transaction status is DELETED with unchanged source code

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page explains the case when the transaction is flagged as deleted in the evolution node, while there is no change in the analyzed code source.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅
8.2.x	✅
8.1.x	✅
8.0.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS2	✅

Step by Step scenario

Run at least 2 snapshots
Connect to TCC
Observe the variation

Action Plan

Transaction Configuration Center - Enhancement - Transactional Functions - Status Variation - Transaction status is MODIFIED with unchanged source code

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page explains the case when the transaction is flagged as MODIFIED in the evolution node, while there is no change in the analyzed code source.

Technically, transaction status is based on the transaction checksum. In a given snapshot, if a transaction has a different checksum than in the previous snapshot, then it is considered as MODIFIED. Transaction checksum is calculated based on the checksums of the objects inside the transaction.

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

Mon, 01 Jan 0001 00:00:00 +0000

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

Release	Yes/No
8.2.x	✅
8.1.x, x <5	✅
8.0.x	✅
7.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS2	✅

Step by Step Scenario

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

Take at least 2 snapshots
Open TCC
Go to evolution node
Select one Transaction
Observe the issue

Action Plan