Oracle 视图 V$XSTREAM_APPLY_READER 官方解释，作用，如何使用详细说明
本站中文解释
Oracle视图 V$XSTREAM_APPLY_READER 是支持 Oracle GoldenGate 概念的视图，该视图用于查看每个采集器的读取速度和采集器统计信息。
该视图提供了 read state、read rowid、read timestamp、read sequence 四个基本字段，可以查看当前采集器读取了多少条数据，以及最后读取数据所 come from 的时间和文件。
当我们想查看 Oracle GoldenGate 采集器的执行状态时，可以使用该视图进行查看。
官方英文解释
V$XSTREAM_APPLY_READER displays information about each XStream apply reader. The apply reader is a process which reads (dequeues) messages from the queue, computes message dependencies, and builds transactions. It passes the transactions on to the coordinator in commit order for assignment to the apply servers. An apply reader is a subcomponent of an apply process, outbound server, or inbound server.
| Column | Datatype | Description |
|---|---|---|
|
|
|
Session ID of the reader’s session |
|
|
|
Serial number of the reader’s session |
|
|
|
Apply process number. An apply process is an Oracle background process, prefixed by |
|
|
|
Name of the apply process |
|
|
|
Shows the state of the apply reader and the hash server. The possible values include:
The state of the apply reader is displayed first, followed by the state of the hash server. A semicolon separates the apply reader state from the hash server state. |
|
|
|
Total number of messages dequeued since the apply process was last started |
|
|
|
Number of messages spilled by the reader since the apply process was last started |
|
|
|
Time when the last message was received |
|
|
|
Number of the last message received |
|
|
|
For captured messages, creation time at the source database of the last message received. For user-enqueued messages, time when the message was enqueued into the queue at the local database. |
|
|
|
Amount (in bytes) of SGA memory used by the apply process since it was last started |
|
|
|
Time elapsed (in hundredths of a second) dequeuing messages since the apply process was last started |
|
|
|
Time elapsed (in hundredths of a second) scheduling messages since the apply process was last started. Scheduling includes computing dependencies between messages and assembling messages into transactions. |
|
|
|
Elapsed time (in hundredths of a second) spent spilling messages since the apply process was last started |
|
|
|
Oldest SCN |
|
|
|
Transaction ID undo segment number of the oldest transaction that either has been applied or is being applied |
|
|
|
Transaction ID slot number of the oldest transaction that either has been applied or is being applied |
|
|
|
Transaction ID sequence number of the oldest transaction that either has been applied or is being applied |
|
|
|
Spill low-watermark SCN |
|
|
|
When the apply process uses combined capture and apply, the session ID of the propagation receiver that is responsible for direct communication between capture and apply. If the apply process does not use combined capture and apply, then this column is |
|
|
|
When the apply process uses combined capture and apply, the serial number of the propagation receiver that is responsible for direct communication between capture and apply. If the apply process does not use combined capture and apply, then this column is |
|
|
|
When the apply process uses combined capture and apply, the process identification number of the propagation receiver that is responsible for direct communication between capture and apply. If the apply process does not use combined capture and apply, then this column is |
|
|
|
When the apply process uses combined capture and apply, the number of bytes received by the apply process from the capture process since the apply process last started. If the apply process does not use combined capture and apply, then this column is not populated. |
|
|
|
Dequeued position. This column is populated only for an apply process that is functioning as an XStream inbound server. |
|
|
|
Spill low-watermark position. This column is populated only for an apply process that is functioning as an XStream inbound server. |
|
|
|
Oldest transaction ID |
|
|
|
Total number of LCRs with row-level dependencies since the apply process last started |
|
|
|
Total number of LCRs with watermark dependencies since the apply process last started. A watermark dependency occurs when an apply process must wait until the apply process’s low watermark reaches a particular threshold. |
|
|
|
Total number of LCRs currently in memory |
|
|
|
The total amount of shared memory (in bytes) allocated from the XStreams pool for the apply process since the apply process last started |
|
|
|
The ID of the container to which the data pertains. Possible values include:
|
Note:
The ELAPSED_SCHEDULE_TIME column is only populated if the TIMED_STATISTICS initialization parameter is set to true, or if the STATISTICS_LEVEL initialization parameter is set to TYPICAL or ALL.
See Also:
-
“TIMED_STATISTICS”
-
“STATISTICS_LEVEL”
