Inconsistent Analysis: The problem as given with transactions T1 and T2 where two transactions interleave to make incorrect result during an analysis by Audit is the instance of such a problem. This problem happens when more than one data items are being used for analysis, whereas another transaction has modified some of that value and some are yet to be modified. Therefore, an analysis transaction reads values from the inconsistent state of the database those results in inconsistent analysis.

Therefore, we can conclude that the prime reason of troubles of concurrent transactions is that a transaction reads an inconsistent state of the database that has been formed by other transaction.

But how do we ensure that implementation of two or more transactions have not resulted in a concurrency related problem?

Well one of the commonest techniques used for this purpose is to restrict access to data items that are being written or read by single transaction and is being written by another transaction. This technique is known as locking.