7.228 V$FLASHBACK_TXN_MODS
V$FLASHBACK_TXN_MODS
displays the individual modifications of all the transactions in memory.
This view is relevant AFTER a compensating transaction has been started through the DBMS_FLASHBACK.TRANSACTION_BACKOUT()
set of functions, and is no longer relevant once the compensating transaction is either committed or rolled back. It also provides a tabular representation of the undo SQL that is not available through the CLOB XML construct in the DBA_FLASHBACK_TXN_REPORT
view.
Column | Datatype | Description |
---|---|---|
|
|
Transaction ID of the compensating transaction |
|
|
Name of the compensating transaction |
|
|
Transaction ID of a relevant transaction found in memory |
|
|
Name of the transaction with |
|
|
Parent transaction ID (for a PDML transaction) |
|
|
If the transaction is in the transaction dependency graph |
|
|
If the transaction is part of the input set provided |
|
|
Order in which the transaction has been backed out |
|
|
Undo SQL for the modification |
|
|
Order in which the given SQL has been executed to back out this transaction |
|
|
If the undo SQL is greater than 4000 bytes, then a sequence number, starting from |
|
|
SQL ID of the undo SQL (used only for this compensating transaction) |
|
|
Operation (such as insert/update/delete) performed by the forward-going operation |
|
|
Indicates whether the transaction has been backed out as of now |
|
|
If the concerned modification is causing a conflict |
|
|
Sometimes an LCR could cause multiple modifications (for example, an update of an IOT could actually be a delete followed by an insert) |
|
|
The ID of the container to which the data pertains. Possible values include:
|
See Also:
-
Oracle Database PL/SQL Packages and Types Reference for more information about the
DBMS_FLASHBACK.TRANSACTION_BACKOUT
procedures