8.35 V$AQ_SHARDED_SUBSCRIBER_STAT
V$AQ_SHARDED_SUBSCRIBER_STAT displays basic statistical information about the subscribers of sharded queues. There is one row per queue per shard per subscriber.
Note:
AQ sharded queues are deprecated in Oracle Database 21c. Oracle recommends that you instead use Transactional Event Queues (TxEventQs) for higher throughput and better performance.| Column | Datatype | Description |
|---|---|---|
|
|
|
Queue identifier |
|
|
|
Subscriber identifier |
|
|
|
Shard identifier |
|
|
|
Priority value of the shard |
|
|
|
Message serial number |
|
|
|
Last known dequeue position in this shard |
|
|
|
Number of enqueued messages |
|
|
|
Number of dequeued messages |
|
|
|
Amount of time spent performing dequeues (in seconds) |
|
|
|
Actual amount of CPU time spent performing dequeues (in seconds) |
|
|
|
Number of messages dequeued per second |
|
|
|
Message ID at the dequeue position of the subscriber in this shard A NULL value indicates that either the shard is empty or no dequeues have been done on this shard. |
|
|
|
Time since last dequeue activity (in seconds) |
|
|
|
Estimated amount of time to drain the shard (in seconds) with current enqueue and dequeue rates. Null, if the enqueue rate is greater than the dequeue rate. |
|
|
|
Estimated amount of time to drain the shard (in seconds) with no new enqueues |
|
|
|
Message latency within the last 5 minutes (in milliseconds). Null if no message is consumed or it is delay dequeue. |
|
|
|
Message latency within the last 1 hour (in milliseconds). Null if no message is consumed or it is delay dequeue. |
|
|
|
Message latency within the last 5 hours (in milliseconds). Null if no message is consumed or it is delay dequeue. |
|
|
|
Number of dequeue attempts A single dequeue call may result in multiple internal dequeue attempts, and this value may not match the number of dequeue calls made by the client. |
|
|
|
Reserved for internal use |
|
|
|
Message ID of the earliest next message (that is, the minimum READY time) with non-zero delay, not yet dequeued by the subscriber |
|
|
|
Reserved for internal use |
|
|
|
Ready time of the earliest next message (that is, the minimum READY time) with non-zero delay, not yet dequeued by the subscriber |
|
|
|
Number of messages that were marked as expired before being dequeued by the subscriber |
|
|
|
Number of messages marked as skipped for rule-based subscribers Messages that do not qualify for the subscriber’s rule are marked as skipped. |
|
|
|
Subshard identifier of the dequeue low watermark |
|
|
|
Sequence number of the dequeue low watermark message
within the subshard identified by
|
|
|
|
Indicates the position of the dequeue low watermark
relative to the message identified by
|
|
|
|
Number of messages whose retention time elapsed before being dequeued by the subscriber and were therefore marked for purging from the queue This count is incremented only when the queue-level
parameter |
|
|
|
The ID of the container to which the data pertains. Possible values include:
|
Footnote 1 This column is available starting with Oracle AI Database 26ai, Release Update 23.26.1.