Advanced Queuing - Oracle

Working with Messaging Gateway
Enabling and Disabling Propagation Jobs
When a schedule is created, it is in an enabled state. This means that if there is an
associated subscriber, the corresponding propagation job will be active. That is, it
will be polling for messages in the source queue. To disable (or enable) a
propagation job, the associated schedule must be disabled (or enabled).
The following examples disable and enable the schedule ‘sch_aq2mq’.
begin
dbms_mgwadm.disable_propagation_schedule(‘sch_aq2mq’);
end;
begin
dbms_mgwadm.enable_propagation_schedule(‘sch_aq2mq’);
end;
Resetting Propagation Jobs
When a problem occurs in propagation, the Messaging Gateway agent retries the
failed operation up to 16 times before the propagation job stops. To restart the
propagation job with the error count reset to zero, use the reset_subscriber( )
procedure.
Restarting a Propagation Job: Example
begin
dbms_mgwadm.reset_subscriber(‘sub_aq2mq’);
end;
Altering Subscribers and Schedules
The following parameters can be altered after the subscriber is created: the selection
rule, the transformation, and the exception queue. The value DBMS_MGWADM.NO_
CHANGE indicates that the value of the parameter has not changed.
Altering Subscribers and Schedules: Example
begin
dbms_mgwadm.alter_subscriber(
subscriber_id => 'sub_aq2mq', -- MGW subscriber name
rule => dbms_mgwadm.NO_CHANGE, -- selection rule not changed
-- not used with MQSeries
transformation => dbms_mgwadm.NO_CHANGE, -- transformation invoked on
-- dequeue not changed
exception_queue => ‘mgwuser.my_ex_queue’); -- register exception
-- queue: same type as source
18-22 Oracle9i Application Developer’s Guide - Advanced Queuing