7.28 V$AQ_SUBSCRIBER_LOAD
V$AQ_SUBSCRIBER_LOAD
describes the load of all subscribers of sharded queues in terms of latency at every instance in an Oracle RAC environment.
Latency denotes the predicted amount of time (in seconds) required from the current time to drain all the messages for that subscriber at each respective instance. The latency calculation considers past enqueue/dequeue rates and future enqueue/dequeue rates based on history.
Column | Datatype | Description |
---|---|---|
|
|
Queue ID |
|
|
Queue schema |
|
|
Queue name |
|
|
Subscriber ID |
|
|
Subscriber name |
|
|
Possible values:
|
|
|
Latency (in seconds). Valid only when |
|
|
Approximate number of dequeue requests noted recently |
|
|
Number of queue shards that have messages for this subscriber |
|
|
Indicates whether the subscriber is actively listening at this instance for messages (TRUE) or not (FALSE) |
|
|
For internal use only |
|
|
An affinity switch is a change in the dequeue instance for a shard-subscriber pair. A mandatory affinity switch is when there are local enqueues in the queue at the instance but no local dequeues present, so the dequeue affinity is switched to another instance for that shard-subscriber pair. This column shows the number of times mandatory affinity switches were needed from this instance to another for this subscriber. |
|
|
Optional affinity switches are affinity switches that are not mandatory. Optional affinity switches are done for global load balancing across the Oracle Real Application Clusters (Oracle RAC) database. This column shows the number of times optional affinity switches were needed from this instance to another for this subscriber. |
|
|
The ID of the container to which the data pertains. Possible values include:
|
See Also:
Oracle Database Advanced Queuing User's Guide for more information about Oracle Database Advanced Queueing