If a transaction is aborted during its active state, it will go in a —

Concept: A DBMS transaction moves through a fixed set of states. On the success path it goes Active -> Partially Committed -> Committed. On the failure path, any error while Active (or Partially Committed) pushes it into the Failed state; from Failed, a rollback runs and it then reaches Aborted, finally settling in Terminated.

Application: Here the abort/error happens while the transaction is still in the Active state -- the exact trigger for the failure path above. So it moves immediately into the Failed state; only after the subsequent rollback does it reach Aborted/Terminated.

• Terminated state -- this is the last stage of the lifecycle, reached only once rollback (after a failure) or a commit has fully completed; it is not the state entered the instant the abort occurs.

• Committed state -- only reached when a transaction finishes all operations successfully and those changes are made permanent; an abort rules this out entirely.

• Partially committed state -- only reached once every operation has executed successfully but before commit is finalised; it belongs to the success path, so an abort during Active execution never reaches it.

So an abort during the Active state takes the transaction to the Failed state.