Advanced Queuing - Oracle

Working with Messaging Gateway
instead of the destination queue. If a subscriber does not have an exception queue
specified, the propagation job stops when message conversion fails.
For outbound propagation, the exception queue must refer to an already existing
AQ queue. The payload type of the source and exception queue must match. The
exception queue must be created as a queue type of NORMAL_QUEUE rather than
EXCEPTION_QUEUE.
For inbound propagation, the exception queue must be a registered non-Oracle
messaging system queue, and the source and exception queues must use the same
messaging system link.
Monitoring Propagation Jobs
You can use the MGW_SUBSCRIBERS view to check the existing configuration of
subscribers and to monitor the status of propagation jobs. In addition to the
configured information, columns in the view indicate the total number of messages
propagated for the job (since the Messaging Gateway agent started), the number of
propagation failures, the status of the propagation job, and error information.
The subscriber status value of ENABLED indicates that the subscriber is enabled.
(Note that this does not mean that the propagation job is enabled. For a propagation
job to be enabled, both the subscriber and an associated schedule must be enabled).
DELETE_PENDING indicates that subscriber removal is pending. This can occur
when DBMS_MGWADM.REMOVE_SUBSCRIBER is called, but certain cleanup tasks
pertaining to this subscriber are still outstanding. In release 9.2, a subscriber’s status
is always ENABLED unless it is DELETE_PENDING.
Error information includes the number of delivery failures, last error message, the
last error date, and the last error time. If the number of failures reaches 16,
propagation stops. Refer to "Resetting Propagation Jobs" on page 18-22.
Checking Propagated Messages: Example
SQL> select subscriber_id, queue_name, propagated_msgs, exceptionq_msgs from
mgw_subscribers;
SUBSCRIBER_ID QUEUE_NAME PROPAGATED_MSGS EXCEPTIONQ_MSGS
--------------------------------------------------------------------
SUB_AQ2MQ MGWUSER.SRCQ 1014 10
Checking for Errors: Example
SQL> select queue_name, failures, last_error_msg from mgw_subscribers where
subscriber_id = ‘SUB_AQ2MQ’;
Messaging Gateway 18-25