This chapter describes the Oracle Database Advanced Queuing (AQ) administrative interface views and Oracle Messaging Gateway (MGW) views.
Note:
All views not detailed in this chapter are described in the Oracle Database Reference.This chapter contains these topics:
ALL_QUEUE_TABLES: Queue Tables Accessible to the Current User
ALL_QUEUE_SUBSCRIBERS: Subscribers for Queues Where User Has Queue Privileges
USER_ATTRIBUTE_TRANSFORMATIONS: User Transformation Functions
AQ$INTERNET_USERS: Oracle Database Advanced Queuing Agents Registered for Internet Access
V$BUFFERED_SUBSCRIBERS: Subscribers for All Buffered Queues in the Instance
V$BUFFERED_PUBLISHERS: All Buffered Publishers in the Instance
V$PERSISTENT_QUEUES: All Active Persistent Queues in the Instance
V$PERSISTENT_SUBSCRIBERS: All Active Subscribers of the Persistent Queues in the Instance
V$PERSISTENT_PUBLISHERS: All Active Publishers of the Persistent Queues in the Instance
V$PROPAGATION_SENDER: Buffer Queue Propagation Schedules on the Sending (Source) Side
V$PROPAGATION_RECEIVER: Buffer Queue Propagation Schedules on the Receiving (Destination) Side
V$SUBSCR_REGISTRATION_STATS: Diagnosability of Notifications
V$STREAMSMETRIC: Streams Metrics for the Most Recent Interval
V$AQ_JOB_COORDINATOR: Performance Statistics per Coordinator
Oracle Messaging Gateway Views
The DBA_QUEUE_TABLES view contains information about the owner instance for a queue table. A queue table can contain multiple queues. In this case, each queue in a queue table has the same owner instance as the queue table. Its columns are the same as those in ALL_QUEUE_TABLES.
The USER_QUEUE_TABLES view is the same as DBA_QUEUE_TABLES with the exception that it only shows queue tables in the user's schema. It does not contain a column for OWNER.
The ALL_QUEUE_TABLES view describes queue tables accessible to the current user.
The DBA_QUEUES view specifies operational characteristics for every queue in a database. Its columns are the same as those ALL_QUEUES. Oracle Database 12c Release 1 (12.1) introduces a new column SHARDED with data type VARCHAR2(5). The value for this column is TRUE for sharded queue, otherwise FALSE.
The USER_QUEUES view is the same as DBA_QUEUES with the exception that it only shows queues in the user's schema. Oracle Database 12c Release 1 (12.1) introduces a new column SHARDED with data type VARCHAR2(5). The value for this column is TRUE for sharded queue, otherwise FALSE.
The ALL_QUEUES view describes all queues on which the current user has enqueue or dequeue privileges. If the user has any Advanced Queuing system privileges, like MANAGE ANY QUEUE, ENQUEUE ANY QUEUE or DEQUEUE ANY QUEUE, this view describes all queues in the database. Oracle Database 12c Release 1 (12.1) introduces a new column SHARDED with data type VARCHAR2(5). The value for this column is TRUE for sharded queue, otherwise FALSE.
The DBA_QUEUE_SCHEDULES view describes all the current schedules in the database for propagating messages.
The USER_QUEUE_SCHEDULES view is the same as DBA_QUEUE_SCHEDULES with the exception that it only shows queue schedules in the user's schema.
The QUEUE_PRIVILEGES view describes queues for which the user is the grantor, grantee, or owner. It also shows queues for which an enabled role on the queue is granted to PUBLIC.
The AQ$<Queue_Table_Name> view describes the queue table in which message data is stored. This view is automatically created with each queue table and should be used for querying the queue data. The dequeue history data (time, user identification and transaction identification) is only valid for single-consumer queues.
In a queue table that is created with the compatible parameter set to '8.1' or higher, messages that were not dequeued by the consumer are shown as "UNDELIVERABLE". You can dequeue these messages by msgid. If the Oracle Database Advanced Queuing queue process monitor is running, then the messages are eventually moved to an exception queue. You can dequeue these messages from the exception queue with an ordinary dequeue.
A multiconsumer queue table created without the compatible parameter, or with the compatible parameter set to '8.0', does not display the state of a message on a consumer basis, but only displays the global state of the message.
Note:
Queues created in a queue table withcompatible set to 8.0 (referred to in this guide as 8.0-style queues) are deprecated in Oracle Database Advanced Queuing 10g Release 2 (10.2). Oracle recommends that any new queues you create be 8.1-style or newer and that you migrate existing 8.0-style queues at your earliest convenience.When a message is dequeued using the REMOVE mode, DEQ_TIME, DEQ_USER_ID, and DEQ_TXN_ID are updated for the consumer that dequeued the message.
You can use MSGID and ORIGINAL_MSGID to chain propagated messages. When a message with message identifier m1 is propagated to a remote queue, m1 is stored in the ORIGINAL_MSGID column of the remote queue.
Beginning with Oracle Database 10g, AQ$Queue_Table_Name includes buffered messages. For buffered messages, the value of MSG_STATE is one of the following:
IN MEMORY
Buffered messages enqueued by a user
DEFERRED
Buffered messages enqueued by a capture process
SPILLED
User-enqueued buffered messages that have been spilled to disk
DEFERRED SPILLED
Capture-enqueued buffered messages that have been spilled to disk
BUFFERED EXPIRED
Expired buffered messages
For JMS Sharded Queues, the columns RETRY_COUNT, EXCEPTION_QUEUE_OWNER, EXCEPTION_QUEUE, PROPAGATED_MSGID, SENDER_NAME, SENDER_ADDRESS, SENDER_PROTOCOL, ORIGINAL_MSGID, ORIGINAL_QUEUE_NAME, ORIGINAL_QUEUE_OWNER, EXPIRATION_REASON are always NULL.
For JMS Sharded Queues, this view shows messages only for durable subscribers because non durable subscribers are session specific. The view returns data from the in-memory Sharded Queue message cache if available, otherwise from the values on disk. A user is required to be one of the following in order to query from AQ$<queue_name> view for Sharded Queues:
user is the owner
user has "dequeue" privilege on queue
user has "dequeue any queue" privilege
The view has the following difference for Sharded Queues:
MSG_PRIORITY is defined as NUMBER(38) in 12c Release 1 (12.1)
MSG_STATE in 12c Release 1 (12.1) queue table doesnt have BUFFERED_EXPIRED hence for 12c Release 1 (12.1) the max length of UNDELIVERABLE is taken as length got MSG_STATE.
EXPIRATION is defined as TIMESTAMP(6) WITH TIME ZONE in 12c Release 1 (12.1) queue table.
USER_DATA column is defined using a decode on USERDATA_RAW and USERDATA_BLOB with UTL_RAW.CAST_TO_VARCHAR2.
CONSUMER_NAME is defined as VARCHAR2(128) in 12c Release 1 (12.1)
Table 9-1 AQ$<Queue_Table_Name> View
| Column | Datatype | NULL | For JMS Sharded Queues 12c Release 1 (12.1) | Description |
|---|---|---|---|---|
|
|
|
- |
Queue name |
|
|
|
|
- |
|
|
|
|
|
- |
|
|
|
|
|
|
Unique identifier of the message |
|
|
|
|
- |
User-provided correlation identifier |
|
|
|
|
- |
|
Message priority |
|
|
|
- |
Message state. 12c Release 1 (12.1) queue table doesnt have |
|
|
|
|
- |
Time in date format at which the message in waiting state would become ready. Equals |
|
|
|
|
- |
Time as a timestamp format at which the message in waiting state would become ready. Equals |
|
|
|
|
- |
|
Number of seconds in which the message expires after being |
|
|
|
- |
|
|
|
|
|
- |
Enqueue time |
|
|
|
|
- |
Enqueue time |
|
|
|
|
- |
Enqueue user ID |
|
|
|
|
- |
Enqueue user name |
|
|
|
|
- |
Enqueue transaction ID |
|
|
|
|
- |
Dequeue time |
|
|
|
|
- |
Dequeue time |
|
|
|
|
- |
Dequeue user ID |
|
|
|
|
- |
Dequeue user name |
|
|
|
|
- |
Dequeue transaction ID |
|
|
|
|
- |
|
Number of retries |
|
|
|
- |
|
Exception queue schema |
|
|
|
- |
|
Exception queue name |
|
|
- |
- |
User data. |
|
|
|
|
- |
|
Name of the agent enqueuing the message (valid only for 8.1-compatible queue tables) |
|
|
|
- |
|
Queue name and database name of the source (last propagating) queue (valid only for 8.1-compatible queue tables). The database name is not specified if the source queue is in the local database. |
|
|
|
- |
|
Protocol for sender address (reserved for future use and valid only for 8.1-compatible queue tables) |
|
|
|
- |
|
Message ID of the message in the source queue (valid only for 8.1-compatible queue tables) |
|
|
|
- |
|
Name of the agent receiving the message (valid only for 8.1-compatible multiconsumer queue tables) |
|
|
|
- |
Queue name and database link name of the agent receiving the message.The database link name is not specified if the address is in the local database. The address is |
|
|
|
|
- |
Protocol for address of receiving agent (valid only for 8.1-compatible queue tables) |
|
|
|
|
- |
|
Message ID of the message in the queue of the receiving agent (valid only for 8.1-compatible queue tables) |
|
|
|
- |
|
Name of the queue the message came from |
|
|
|
- |
|
Owner of the queue the message came from |
|
|
|
- |
|
Reason the message came into exception queue. Possible values are |
Note:
A message is moved to an exception queue ifRETRY_COUNT is greater than MAX_RETRIES. If a dequeue transaction fails because the server process dies (including ALTER SYSTEM KILL SESSION) or SHUTDOWN ABORT on the instance, then RETRY_COUNT is not incremented.The AQ$<Queue_Table_Name_S> view provides information about subscribers for all the queues in any given queue table. It shows subscribers created by users with DBMS_AQADM.ADD_SUBSCRIBER and subscribers created for the apply process to apply user-created events. It also displays the transformation for the subscriber, if it was created with one. It is generated when the queue table is created.
This view provides functionality that is equivalent to the DBMS_AQADM.QUEUE_SUBSCRIBERS() procedure. For these queues, Oracle recommends that the view be used instead of this procedure to view queue subscribers. This view is created only for 8.1-compatible queue tables.
Table 9-2 AQ$<Queue_Table_Name_S> View
| Column | Datatype | NULL | Description |
|---|---|---|---|
|
|
|
|
Name of queue for which subscriber is defined |
|
|
|
- |
Name of agent |
|
|
|
- |
Address of agent |
|
|
|
- |
Protocol of agent |
|
|
|
- |
Name of the transformation (can be null) |
The AQ$<Queue_Table_Name_R> view displays only the subscribers based on rules for all queues in a given queue table, including the text of the rule defined by each subscriber. It also displays the transformation for the subscriber, if one was specified. It is generated when the queue table is created.
This view is created only for 8.1-compatible queue tables.
Table 9-3 AQ$<Queue_Table_Name_R> View
| Column | Datatype | NULL | Description |
|---|---|---|---|
|
|
|
|
Name of queue for which subscriber is defined |
|
|
|
- |
Name of agent |
|
|
|
- |
Address of agent |
|
|
|
- |
Protocol of agent |
|
|
|
- |
Text of defined rule |
|
|
|
- |
Set of rules |
|
|
|
- |
Name of the transformation (can be null) |
The DBA_QUEUE_SUBSCRIBERS view returns a list of all subscribers on all queues in the database. Its columns are the same as those in ALL_QUEUE_SUBSCRIBERS.
The USER_QUEUE_SUBSCRIBERS view returns a list of subscribers on queues in the schema of the current user. Its columns are the same as those in ALL_QUEUE_SUBSCRIBERS except that it does not contain the OWNER column.
The ALL_QUEUE_SUBSCRIBERS view returns a list of subscribers to queues that the current user has privileges to dequeue from.
The DBA_TRANSFORMATIONS view displays all the transformations in the database. These transformations can be specified with Advanced Queue operations like enqueue, dequeue and subscribe to automatically integrate transformations in messaging. This view is accessible only to users having DBA privileges.
The DBA_ATTRIBUTE_TRANSFORMATIONS view displays the transformation functions for all the transformations in the database.
The USER_TRANSFORMATIONS view displays all the transformations owned by the user. To view the transformation definition, query USER_ATTRIBUTE_TRANSFORMATIONS.
The USER_ATTRIBUTE_TRANSFORMATIONS view displays the transformation functions for all the transformations of the user.
The DBA_SUBSCR_REGISTRATIONS view lists all the subscription registrations in the database.
The USER_SUBSCR_REGISTRATIONS view lists the subscription registrations in the database for the current user. Its columns are the same as those in DBA_SUBSCR_REGISTRATIONS.
The AQ$INTERNET_USERS view provides information about the agents registered for Internet access to Oracle Database Advanced Queuing. It also provides the list of database users that each Internet agent maps to.
Table 9-6 AQ$INTERNET_USERS View
| Column | Datatype | NULL | Description |
|---|---|---|---|
|
|
|
- |
Name of the Oracle Database Advanced Queuing Internet agent |
|
|
|
- |
Name of database user that this Internet agent maps to |
|
|
|
- |
Indicates whether this agent is allowed to access Oracle Database Advanced Queuing through HTTP ( |
|
|
|
- |
Indicates whether this agent is allowed to access Oracle Database Advanced Queuing through FTP (always |
The V$AQ view provides information about the number of messages in different states for the whole database.
In a Oracle Real Application Clusters environment, each instance keeps its own Oracle Database Advanced Queuing statistics information in its own System Global Area (SGA), and does not have knowledge of the statistics gathered by other instances. When a GV$AQ view is queried by an instance, all other instances funnel their Oracle Database Advanced Queuing statistics information to the instance issuing the query.
The V$BUFFERED_QUEUES view displays information about all buffered queues in the instance. There is one row per queue.
The V$BUFFERED_SUBSCRIBERS view displays information about the subscribers for all buffered queues in the instance. There is one row per subscriber per queue.
The V$BUFFERED_PUBLISHERS view displays information about all buffered publishers in the instance. There is one row per queue per sender. The values are reset to zero when the database (or instance in an Oracle RAC environment) restarts.
The V$PERSISTENT_QUEUES view displays information about all active persistent queues in the database since the queues' first activity time. There is one row per queue. The rows are deleted when the database (or instance in an Oracle RAC environment) restarts.
The V$PERSISTENT_QMN_CACHE view displays detailed statistics about all background activities relating to all queue tables in the database. There is one row per queue table. The values are reset when the database (or instance in an Oracle RAC environment) restarts.
The V$PERSISTENT_SUBSCRIBERS view displays information about all active subscribers of the persistent queues in the database. There is one row per instance per queue per subscriber. The rows are deleted when the database (or instance in an Oracle RAC environment) restarts.
The V$PERSISTENT_PUBLISHERS view displays information about all active publishers of the persistent queues in the database. There is one row per instance per queue per publisher. The rows are deleted when the database (or instance in an Oracle RAC environment) restarts.
See Also:
Oracle Database Reference for more information about V$PERSISTENT_PUBLISHERS.The V$PROPAGATION_SENDER view displays information about buffer queue propagation schedules on the sending (source) side. The values are reset to zero when the database (or instance in a Oracle Real Application Clusters (Oracle RAC) environment) restarts, when propagation migrates to another instance, or when an unscheduled propagation is attempted.
The V$PROPAGATION_RECEIVER view displays information about buffer queue propagation schedules on the receiving (destination) side. The values are reset to zero when the database (or instance in a Oracle Real Application Clusters (Oracle RAC) environment) restarts, when propagation migrates to another instance, or when an unscheduled propagation is attempted.
The V$SUBSCR_REGISTRATION_STATS view provides information for diagnosability of notifications.
This V$METRICGROUP view displays information about the metric group for each of the four major Streams components: capture, propagation, apply, and queue.
This view displays the capture, propagation, and apply metrics for the most recent interval.
Table 9-7 GV$STREAMSMETRIC View
| Column | Datatype | Description |
|---|---|---|
|
|
Instance |
ID (GV$ only) |
|
|
|
Begin time of interval |
|
|
|
End time of interval |
|
|
|
Interval size (centi-seconds) |
|
|
|
Type of the component (either ' |
|
|
|
Name of streams component |
|
|
|
Time that component started |
|
|
|
Value of rate 1 |
|
|
|
Name of rate1 |
|
|
|
Unit of measurement of rate1 |
|
|
|
Value of rate 2 |
|
|
|
Name of rate2 |
|
|
|
Unit of measurement of rate2 |
|
|
|
Latency from time last message processed by component was written to redo to time the message was processed by this component |
This view returns all metric values for streams messages over the past hour. It has the same form as V$STREAMSMETRIC: Streams Metrics for the Most Recent Interval.
This view displays view provides catalog access to streams metric history.
Table 9-8 DBA_HIST_STREAMSMETRIC View
| Column | Datatype | Description |
|---|---|---|
|
|
|
Required by AWR, snapshot ID |
|
|
|
Required by AWR, database ID |
|
|
|
Required by AWR, instance number |
|
|
|
Begin time of interval |
|
|
|
End time of interval |
|
|
|
Interval size (centi-seconds) |
|
|
|
Type of the component (either ' |
|
|
|
Name of streams component |
|
|
|
Time that component started |
|
|
|
Value of rate 1 |
|
|
|
Value of rate 2 |
|
|
|
Latency from time last message processed by component was written to redo to time the message was processed by this component |
This view displays view provides catalog access to queue metric history.
Table 9-9 DBA_ATTRIBUTE_TRANSFORMATIONS View
| Column | Datatype | Description |
|---|---|---|
|
|
|
Required by AWR, snapshot ID |
|
|
|
Required by AWR, database ID |
|
|
|
Required by AWR, instance number |
|
|
|
Name of queue process |
|
|
|
Time when queue started |
|
|
|
Begin time of interval |
|
|
|
End time of interval |
|
|
|
Interval size (centi-seconds) |
|
|
|
Messages enqueue per second |
|
|
|
Messages spilled per second |
|
|
|
Number of messages in the queue |
The V$AQ_BACKGROUND_COORDINATOR view is applicable for Oracle Database 12c Release 1 (12.1) onwards. This view lists performance statistics for the Oracle Database Advanced Queueing master background coordinator process (AQPC).
The V$AQ_JOB_COORDINATOR view is applicable for Oracle Database 12c Release 1 (12.1) onwards. This view lists performance statistics per coordinator, for every AQ coordinator controlled by the AQ's Master coordinator.
The V$AQ_SERVER_POOL view is applicable for Oracle Database 12c Release 1 (12.1) onwards. This view lists performance statistics for all the servers in the pool.
The V$AQ_CROSS_INSTANCE_JOBS view is applicable for Oracle Database 12c Release 1 (12.1) onwards. This view describes each of the cross process jobs. Each job serves for forwarding messages for a shard from source instance to destination instance for a set of subscribers.
The V$AQ_NONDUR_REGISTRATIONS view is applicable for Oracle Database 12c Release 1 (12.1) onwards. This view provides information about non-durable subscriptions.
The V$AQ_NOTIFICATION_CLIENTS view is applicable for Oracle Database 12c Release 1 (12.1) onwards. This view displays performance statistics for secure OCI client connections.
The V$AQ_SUBSCRIBER_LOAD view is applicable for Oracle Database 12c Release 1 (12.1) onwards. This view 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.
The V$AQ_NONDUR_SUBSCRIBER view is applicable for Oracle Database 12c Release 1 (12.1) onwards. V$AQ_NONDUR_SUBSCRIBER provides information about non-durable subscribers on sharded queues.
The V$AQ_NONDUR_SUBSCRIBER_LWM view is applicable for Oracle Database 12c Release 1 (12.1) onwards. The LWM of a non durable subscriber is a combination of shard, priority and LWM (sub-shard).
The V$AQ_BMAP_NONDUR_SUBSCRIBERS view is applicable for Oracle Database 12c Release 1 (12.1) onwards. This view is used to get the available bit positions. The view is queried to get the free bit position during creation of non durable subscriber.
The V$AQ_MESSAGE_CACHE view provides performance statistics of the message cache for sharded queues at the subshard level in the instance.
This view lists configuration and status information for Messaging Gateway.
Table 9-10 MGW_GATEWAY View Properties
| Name | Type | Description |
|---|---|---|
|
|
|
The database connect string used by the Messaging Gateway agent. |
|
|
|
The database instance on which the Messaging Gateway agent is currently running. This should be |
|
|
|
[Deprecated] Job number of the queued job used to start the Messaging Gateway agent process. The job number is set when Messaging Gateway is started and cleared when it shuts down. |
|
|
|
Name of the Messaging Gateway agent |
|
|
|
Gateway agent ping status. Values:
|
|
|
|
The time when the Messaging Gateway agent job currently running was started. This should be |
|
|
|
Status of the Messaging Gateway agent. Values:
|
|
|
|
Database user name used by the Messaging Gateway agent to connect to the database |
|
|
|
Comments for the agent |
|
|
|
Connection type used by the agent:
|
|
|
|
Name of the Messaging Gateway initialization file used by the agent. |
|
|
|
Date of last Messaging Gateway agent error. The last error information is cleared when Messaging Gateway is started. It is set if the Messaging Gateway agent fails to start or terminates due to an abnormal condition. |
|
|
|
Message for last Messaging Gateway agent error |
|
|
|
Time of last Messaging Gateway agent error |
|
|
|
[Deprecated] Maximum number of messaging connections to Oracle Database |
|
|
|
Maximum heap size used by the Messaging Gateway agent (in MB) |
|
|
|
Maximum number of messaging threads created by the Messaging Gateway agent |
|
|
|
Name of the database service that is associated with an Oracle Scheduler job class used by the agent |
This view lists supplemental options and properties for a Messaging Gateway agent.
Table 9-11 MGW_AGENT_OPTIONS View
| Column | Type | Description |
|---|---|---|
|
|
|
Name of the Messaging Gateway agent |
|
|
|
Indicates whether the value is stored as encrypted:
|
|
|
|
Name of the option |
|
|
|
Option type or usage: |
|
|
|
Value for the option. This will be << |
This view lists the names and types of messaging system links currently defined.
Table 9-12 MGW_LINKS View Properties
| Name | Type | Description |
|---|---|---|
|
|
|
Name of the Messaging Gateway agent that will process propagation jobs for this link |
|
|
|
User comment for the link |
|
|
|
Name of the messaging system link |
|
|
|
Type of messaging system link. Values
|
This view lists information for the WebSphere MQ messaging system links. The view includes most of the messaging system properties specified when the link is created.
Table 9-13 MGW_MQSERIES_LINKS View Properties
| Name | Type | Description |
|---|---|---|
|
|
|
Name of the Messaging Gateway agent that will process propagation jobs for this link |
|
|
|
Connection channel |
|
|
|
Name of the WebSphere MQ host |
|
|
|
Inbound propagation log queue |
|
|
|
Messaging interface type. Values:
|
|
|
|
User comment for the link |
|
|
|
Name of the messaging system link |
|
|
|
Maximum number of messaging connections |
|
|
|
Link options |
|
|
|
Outbound propagation log queue |
|
|
|
Port number |
|
|
|
Name of the WebSphere MQ queue manager |
This view lists information for TIB/Rendezvous messaging system links. The view includes most of the messaging system properties specified when the link was created.
Table 9-14 MGW_TIBRV_LINKS View Properties
| Property Name | Type | Description |
|---|---|---|
|
|
|
Name of the Messaging Gateway agent that will process propagation jobs for this link |
|
|
|
TIB/Rendezvous CM ledger file name |
|
|
|
TIB/Rendezvous CM correspondent name |
|
|
|
TIB/Rendezvous daemon parameter for RVD transport |
|
|
|
User comment for the link |
|
|
|
Name of the messaging system link |
|
|
|
TIB/Rendezvous network parameter for rvd transport |
|
|
|
Link options |
|
|
|
TIB/Rendezvous service parameter for rvd transport |
This view lists information for foreign queues. The view includes most of the queue properties specified when the queue is registered.
Table 9-15 MGW_FOREIGN_QUEUES View Properties
| Name | Type | Description |
|---|---|---|
|
|
|
Queue domain type. Values:
|
|
|
|
Name of the messaging system link |
|
|
|
Name of the registered queue |
|
|
|
Optional queue properties |
|
|
|
Message provider (native) queue name |
|
|
|
User comment for the foreign queue |
This view lists information for Messaging Gateway propagation jobs. The view includes most of the job properties specified when the propagation job was created, as well as other status and statistical information.
| Column | Type | Description |
|---|---|---|
|
|
|
Name of the Messaging Gateway agent that processes this job |
|
|
|
Comments for the propagation job |
|
|
|
Destination queue to which messages are propagated |
|
|
|
Indicates whether the job is enabled or not:
|
|
|
|
Exception queue used for propagation logging purposes |
|
|
|
Option type or usage: |
|
|
|
Number of messages moved to exception queue since the last time the agent was started |
|
|
|
Name of the propagation job |
|
|
|
Message for the last propagation error |
|
|
|
Date of the last propagation error |
|
|
|
Time of the last propagation error |
|
|
|
Name of the Messaging Gateway link used by this job |
|
|
|
Job options |
|
|
|
Propagation poll interval (in seconds) |
|
|
|
Number of messages propagated since the last time the agent was started |
|
|
|
Message propagation style:
|
|
|
|
Propagation type:
|
|
|
|
Subscription rule used for the propagation source |
|
|
|
Source queue from which messages are propagated |
|
|
|
Job status:
|
|
|
|
Transformation used for message conversion |
This view lists configuration and status information for Messaging Gateway subscribers. The view includes most of the subscriber properties specified when the subscriber is added, as well as other status and statistical information.
Table 9-17 MGW_SUBSCRIBERS View Properties
| Name | Type | Description |
|---|---|---|
|
|
|
Destination queue to which messages are propagated |
|
|
|
Number of messages moved to the propagation exception queue since the last time the agent was started |
|
|
|
Exception queue used for logging purposes |
|
|
|
Number of propagation failures |
|
|
|
Date of last propagation error |
|
|
|
Message for last propagation error |
|
|
|
Time of last propagation error |
|
|
|
Subscriber options |
|
|
|
Message propagation style. Values:
|
|
|
|
Number of messages propagated to the destination queue since the last time the agent was started |
|
|
|
Propagation type. Values:
|
|
|
|
Subscriber source queue |
|
|
|
Subscription rule |
|
|
|
Subscriber status. Values:
|
|
|
|
Propagation subscriber identifier |
|
|
|
Transformation used for message conversion |
This view lists configuration and status information for Messaging Gateway schedules. The view includes most of the schedule properties specified when the schedule is created, as well as other status information.
Table 9-18 MGW_SCHEDULES View Properties
| Name | Type | Description |
|---|---|---|
|
|
|
Propagation destination |
|
|
|
Propagation window latency (in seconds) |
|
|
|
Reserved for future use |
|
|
|
Propagation type. Values:
|
|
|
|
Reserved for future use |
|
|
|
Indicates whether the schedule is disabled. |
|
|
|
Propagation schedule identifier |
|
|
|
Propagation source |
|
|
|
Reserved for future use |
|
|
|
Reserved for future use |