Advanced Queuing - Oracle

* Check if the schedule has been enabled: */
SELECT schedule_disabled FROM user_queue_schedules;
/* Unschedule propagation for booked orders: */
EXECUTE dbms_aqadm.unschedule_propagation( \
queue_name => ’OE.OE_bookedorders_que’);
/* Wait for some time for call to be effected: */
EXECUTE dbms_lock.sleep(30);
/* Check if the schedule has been dropped
SELECT * FROM user_queue_schedules;
Visual Basic (OO4O): Example Code
This functionality is currently not available.
Java (JDBC): Example Code
No example is provided with this release.
Propagation of Messages with LOB Attributes
Large Objects can be propagated using AQ using two methods:
Propagation Features
Propagation from RAW queues. In RAW queues the message payload is stored
as a Binary Large Object (BLOB). This allows users to store up to 32KB of data
when using the PL/SQL interface and as much data as can be contiguously
allocated by the client when using OCI. This method is supported by all
releases after 8.0.4 inclusive.
Propagation from Object queues with LOB attributes. The user can populate the
LOB and read from the LOB using Oracle's LOB handling routines. The LOB
attributes can be BLOBs or CLOBs (not NCLOBs). If the attribute is a CLOB AQ
will automatically perform any necessary characterset conversion between the
source queue and the destination queue. This method is supported by all
releases from 8.1.3 inclusive.
See Also: Oracle9i Application Developer’s Guide - Large Objects
(LOBs)
A Sample Application Using AQ 8-111