9.57 V$LOGMNR_SESSION
V$LOGMNR_SESSION displays information about active LogMiner persistent sessions.
               
(A LogMiner persistent session is created either by starting Data Guard SQL Apply on a logical standby database for the first time or by creating Replication capture.) Transient LogMiner sessions (those created as a result of querying the V$LOGMNR_CONTENTS view) do not show up in the V$LOGMNR_SESSION view. The statistics shown in this view correspond to snapshots of the system and are not cumulative in nature.
                  
| Column | Datatype | Description | 
|---|---|---|
| 
 | 
 | Unique identifier for the LogMiner persistent session | 
| 
 | 
 | Unique session name | 
| 
 | 
 | Current state of the LogMiner persistent session: 
 | 
| 
 | 
 | Global database name for the source database | 
| 
 | 
 | Database identifier of the source database | 
| 
 | 
 | System change number (SCN) when the session started | 
| 
 | 
 | Time of the  | 
| 
 | 
 | The time when the session started | 
| 
 | 
 | Number of processes allocated to this session | 
| 
 | 
 | Amount of memory allocated for this chunk | 
| 
 | 
 | System change number (SCN) at start of the session | 
| 
 | 
 | System change number (SCN) at end of the session | 
| 
 | 
 | In the event of a restart, redo records with an SCN lower than this will not be read from the archived redo log files | 
| 
 | 
 | The  | 
| 
 | 
 | The  | 
| 
 | 
 | The  | 
| 
 | 
 | The  | 
| 
 | 
 | LogMiner has delivered all transactions that committed below this SCN to the client | 
| 
 | 
 | Client has consumed and released all transactions that committed below this SCN. | 
| 
 | 
 | Maximum amount of shared memory (in bytes) that LogMiner is allowed to consume | 
| 
 | 
 | Amount of shared memory (in bytes) actually consumed by LogMiner | 
| 
 | 
 | Amount of redo (in bytes) in the current work unit being processed by the BUILDER process. | 
| 
 | 
 | Amount of redo (in bytes) that has been prepared by LogMiner | 
| 
 | 
 | Amount of redo records (in bytes) that are ready, but are yet to be consumed by the client | 
| 
 | 
 | Number of transaction chunks ready for consumption | 
| 
 | 
 | Number of committed transactions ready for consumption. This is less than, or equal to,  | 
| 
 | 
 | Number of transaction chunks that the client currently has in its possession | 
| 
 | 
 | Number of committed transaction chunks that the client is currently working on. This is less than, or equal to, the value of the  | 
| 
 | 
 | Number of transactions pinned (the client is actively working on) | 
| 
 | 
 | Number of committed transactions pinned (the client is actively working on) | 
| 
 | 
 | Checkpoint interval | 
| 
 | 
 | The ID of the container to which the data pertains. Possible values include: 
 | 
See Also: