9.50 V$LOGMNR_CONTENTS
V$LOGMNR_CONTENTS
contains log history information. To query this view, you must have the LOGMINING
privilege.
When a SELECT
statement is executed against the V$LOGMNR_CONTENTS
view, the archive redo log files are read sequentially. Translated records from the redo log files are returned as rows in the V$LOGMNR_CONTENTS
view. This continues until either the filter criteria specified at startup (EndTime
or endScn
) are met or the end of the archive log file is reached.
When this view is queried from a PDB, it returns only redo generated by that PDB.
Column | Datatype | Description |
---|---|---|
|
|
System change number (SCN) when the database change was made |
|
|
System change number (SCN) when the transaction that contains this change started; only meaningful if the |
|
|
System change number (SCN) when the transaction committed; only meaningful if the |
|
|
Timestamp when the database change was made |
|
|
Timestamp when the transaction that contains this change started; only meaningful if the |
|
|
Timestamp when the transaction committed; only meaningful if the |
|
|
Transaction ID undo segment number of the transaction that generated the change |
|
|
Transaction ID slot number of the transaction that generated the change |
|
|
Transaction ID sequence number of the transaction that generated the change |
|
|
Raw representation of the transaction identifier |
|
|
Parent transaction ID undo segment number of a parallel transaction |
|
|
Parent transaction ID slot number of a parallel transaction |
|
|
Parent transaction ID sequence number of a parallel transaction |
|
|
Raw representation of the parent transaction identifier |
|
|
Name of the transaction that made the change; only meaningful if the transaction is a named transaction |
|
|
User level SQL operation that made the change:
The |
|
|
Number of the operation code:
|
|
|
1 = if the redo record was generated because of a partial or a full rollback of the associated transaction 0 = otherwise |
|
|
Owner of the modified data segment |
|
|
Name of the modified data segment |
|
|
Name of the modified table (in case the redo pertains to a table modification) |
|
|
Type of the modified data segment:
|
|
|
Segment type name:
|
|
|
Name of the tablespace containing the modified data segment. This column is not populated for rows where the value of the |
|
|
Row ID of the row modified by the change (only meaningful if the change pertains to a DML). This will be NULL if the redo record is not associated with a DML. |
|
|
Name of the user who executed the transaction |
|
|
Name of the operating system user |
|
|
Machine from which the user connected to the database |
|
|
Audit session ID associated with the user session making the change |
|
|
Session number of the session that made the change |
|
|
Serial number of the session that made the change |
|
|
Information about the database session that executed the transaction. Contains process information, machine name from which the user logged in, and so on. A possible
|
|
|
Number of the thread that made the change to the database |
|
|
Sequence number of the SQL statement within the transaction. If you are mining without the |
|
|
Sequence# associated with the Redo Block Address (RBA) of the redo record associated with the change |
|
|
RBA block number within the log file |
|
|
RBA byte offset within the block |
|
|
Undo Block Address (UBA) file number identifying the file containing the undo block |
|
|
UBA block number for the undo block |
|
|
UBA record index within the undo block |
|
|
UBA undo block sequence number |
|
|
Data block absolute file number of the block changed by the transaction |
|
|
Data block relative file number. The file number is relative to the tablespace of the object. |
|
|
Data block number within the file |
|
|
Data block object number identifying the object |
|
|
Version number of the table being modified |
|
|
Data block data object number identifying the object within the tablespace |
|
|
Reconstructed SQL statement that is equivalent to the original SQL statement that made the change. Refer to Oracle Database
Utilities before executing LogMiner does not generate SQL redo for temporary tables. In such a case, this column will contain the string |
|
|
Reconstructed SQL statement that can be used to undo the effect of the original statement that made the change. DDL statements have no corresponding LogMiner does not generate SQL undo for temporary tables. In such a case, this column will contain the string |
|
|
Record set ID. The tuple ( |
|
|
SQL sequence number. Used in conjunction with |
|
|
Continuation SQL flag. Possible values are:
|
|
|
Informational message about the row. For instance, the string "USER DDL" indicates that the DDL statement returned in the |
|
|
A value of A value of |
|
|
Used as input to the |
|
|
Used as input to the |
|
|
Reserved for future use |
|
|
This column is deprecated in favor of the |
|
|
Object identifier for DMLs to XMLType tables. For changes to non-typed tables, this column is NULL. |
|
|
Identifies the edition in which a DDL statement was executed |
|
|
Client identifier in the session that performed the operation, if available. |
|
|
Contains the pluggable database (PDB) name. This information will only be available when mining with a current LogMiner dictionary. |
|
|
Contains the PDB ID (the PDB_ID column from the DBA_PDBS view). This information will be available only with a current LogMiner dictionary. |
|
|
Contains the PDB UID (the CON_UID column from the DBA_PDBS view). This information will be available with or without a current LogMiner dictionary. |
|
|
Contains the PDB identifier (the DBID column from the DBA_PDBS view). This information will only be available when mining with a current LogMiner dictionary. |
|
|
Contains the GUID associated with the PDB (the GUID column from the DBA_PDBS view). This information will only be available when mining with a current LogMiner dictionary. |
|
|
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_LOGMNR
package -
Oracle Database PL/SQL Packages and Types Reference for more information about the
DBMS_LOB
package