Advanced Queuing - Oracle

dequeue_options.navigation := DBMS_AQ.FIRST_MESSAGE;
LOOP
BEGIN
DBMS_AQ.DEQUEUE(queue_name => ’msggroup_queue’,
dequeue_options => dequeue_options,
message_properties => message_properties,
payload => message,
msgid => message_handle);
DBMS_OUTPUT.PUT_LINE (’Message: ’ || message.subject ||
’ ... ’ || message.text );
dequeue_options.navigation := DBMS_AQ.NEXT_MESSAGE;
Enqueuing and Dequeuing Of Messages
EXCEPTION
WHEN end_of_group THEN
DBMS_OUTPUT.PUT_LINE (’Finished processing a group of messages’);
COMMIT;
dequeue_options.navigation := DBMS_AQ.NEXT_TRANSACTION;
END;
END LOOP;
EXCEPTION
WHEN no_messages THEN
DBMS_OUTPUT.PUT_LINE (’No more messages’);
END;
Enqueuing and Dequeuing Object Type Messages That Contain LOB Attributes Using
PL/SQL
/* Create the message payload object type with one or more LOB attributes. On
enqueue, set the LOB attribute to EMPTY_BLOB. After the enqueue completes,
before you commit your transaction. Select the LOB attribute from the
user_data column of the queue table or queue table view. You can now
use the LOB interfaces (which are available through both OCI and PL/SQL) to
write the LOB data to the queue. On dequeue, the message payload
will contain the LOB locator. You can use this LOB locator after
the dequeue, but before you commit your transaction, to read the LOB data.
*/
/* Setup the accounts: */
connect system/manager
Oracle Advanced Queuing by Example A-53