Advanced Queuing - Oracle

Propagation Features
PL/SQL (DBMS_AQADM Package): Example Code
CONNECT OE/OE;
/* get averages
select avg_time, avg_number, avg_size from user_queue_schedules;
/* get totals
select total_time, total_number, total_bytes from user_queue_schedules;
/* get maximums for a window
select max_number, max_bytes from user_queue_schedules;
/* get current status information of schedule
select process_name, session_id, instance, schedule_disabled
from user_queue_schedules;
/* get information about last and next execution
select last_run_date, last_run_time, next_run_date, next_run_time
from user_queue_schedules;
/* get last error information if any
select failures, last_error_msg, last_error_date, last_error_time
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.
Exception Handling During Propagation
When system errors such as a network failure occur, Advanced Queuing continues
to attempt to propagate messages using an exponential backoff algorithm. In some
situations that indicate application errors, AQ will mark messages as
UNDELIVERABLE if there is an error in propagating the message.
Examples of such errors are when the remote queue does not exist or when there is
a type mismatch between the source queue and the remote queue. In such situations
users must query the DBA_SCHEDULES view to determine the last error that
occurred during propagation to a particular destination. The trace files in the
$ORACLE_HOME/log directory can provide additional information about the error.
8-116 Oracle9i Application Developer’s Guide - Advanced Queuing