V$AQ_NONDUR_SUBSCRIBER

8.25 V$AQ_NONDUR_SUBSCRIBER

V$AQ_NONDUR_SUBSCRIBER provides information about the non-durable subscriptions on sharded queues.

Note:

AQ sharded queues are deprecated in Oracle Database 21c. Oracle recommends that you instead use Transactional Event Queues (TEQs) for higher throughput and better performance.

Column	Datatype	Description
`QUEUE_ID`	`NUMBER`	Queue ID
`SUBSCRIBER_ID`	`NUMBER`	ID of the non-durable subscriber
`SUBSCRIBER_NAME`	`VARCHAR2(128)`	Subscriber name
`RULE_CONDITION`	`VARCHAR2(4000)`	Rule condition of the subscriber
`TRANSFORMATION_OWNER`	`VARCHAR2(128)`	Owner of the transformation (for JMS queues)
`TRANSFORMATION_NAME`	`VARCHAR2(128)`	Name of the transformation (for JMS queues)
`CREATION_TIME`	`TIMESTAMP(1) WITH TIME ZONE`	Non-durable subscriber creation time
`FLAGS`	`NUMBER`	Property of the subscriber: `0x0001` – Persistent subscriber `0x0002` – Buffered subscriber `0x0004` – JMS subscriber `0x0008` – Rule-based subscriber `0x0010` – Subscriber has transformation `0x0020` – Notification-only non-durable subscriber subscriber
`SUBSCRIBER_TYPE`	`NUMBER`	Type of subscriber: `1` – JMS non-durable subscriber `2` – Service layer dummy non-durable subscriber `3` – Notification-only non-durable subscriber
`BITPOS`	`NUMBER`	Position of subscriber in subscriber bitmap
`CON_ID`	`NUMBER`	The ID of the container to which the data pertains. Possible values include: `0`: This value is used for rows containing data that pertain to the entire CDB. This value is also used for rows in non-CDBs. `1`: This value is used for rows containing data that pertain to only the root n: Where n is the applicable container ID for the rows containing data