10.44 V$SHARD_APPLY_COORDINATOR
V$SHARD_APPLY_COORDINATOR
displays information about apply coordinator processes.
Column | Datatype | Description |
---|---|---|
|
|
Session identifier of the apply coordinator process |
|
|
Session serial number of the apply coordinator process |
|
|
Apply coordinator state:
|
|
|
Apply process number An apply process is an Oracle background process, prefixed by |
|
|
Name of the apply process |
|
|
Number of transactions applied by the apply process since the apply process was last started |
|
|
Number of times, since the apply process was last started, that an apply server waited to apply a logical change record (LCR) in a transaction until another apply server applied a transaction, because of a dependency between the transactions |
|
|
Number of times, since the apply process was last started, that an apply server waited to commit a transaction until another apply server committed a transaction to serialize commits |
|
|
Number of administrative jobs issued since the apply process was last started |
|
|
Number of transactions assigned to apply servers since the apply process was last started |
|
|
Number of transactions received by the coordinator process since the apply process was last started |
|
|
Number of transactions that were received by the coordinator, but were ignored because they had been previously applied |
|
|
Number of transactions that were rolled back due to unexpected contention |
|
|
Number of transactions applied by the apply process that resulted in an apply error since the apply process was last started |
|
|
Number of unassigned complete transactions |
|
|
Auto-tuned transaction buffer size |
|
|
Time at which the LCR with the lowest log index was recorded The creation time of the LCR with the lowest LCR log index was also recorded at this time. |
|
|
LCRs with a commit log index less than or equal to this number have definitely been applied, but some LCRs with a higher commit log index also may have been applied. |
|
|
Time at which the LCR corresponding to the low watermark was created |
|
|
Time at which the LCR with the highest log index was recorded The creation time of the LCR with the highest LCR log index was also recorded at this time. |
|
|
No LCR with a commit log index greater than this LCR log index has been applied |
|
|
Time at which the LCR corresponding to the high watermark was created |
|
|
Apply coordinator process start time |
|
|
Time elapsed (in hundredths of a second) spent scheduling transactions since the apply process was last started |
|
|
Elapsed idle time (in hundredths of a second) since the apply process was last started |
|
|
LCR log index currently processed by the apply coordinator |
|
|
Number of active servers |
|
|
Replication unit (RU) identifier |
|
|
Database identifier |
|
|
The ID of the container to which the data pertains. Possible values include:
|
Note:
This view is available starting with Oracle Database 23ai.