Purpose

Usage Notes

The default value of the compatible parameter depends on the database compatibility mode in the init.ora

If the database is in 8.1 or higher compatible mode, the default value is '8.1'

If the database is in 8.0 compatible mode, the default value is '8.0'

The sort keys for dequeue ordering, if any, need to be defined at table creation time. The following objects are created at this time:

The default exception queue associated with the queue table called aq$_<queue_table_name>_e.

A read-only view which is used by AQ applications for querying queue data called aq$<queue_table_name>.

An index for the queue monitor operations called aq$_<queue_table_name>_t.

An index or an index organized table (IOT) in the case of multiple consumer queues for dequeue operations called aq$_<queue_table_name>_i.

For 8.1-compatible multiconsumer queue tables, the following additional objects are created:

A table called aq$_<queue_table_name>_s. This table stores information about the subscribers.

A table called aq$_<queue_table_name>_r. This table stores information about rules on subscriptions.

An index organized table (IOT) called aq$_<queue_table_name>_h.This table stores the dequeue history data.

CLOB, BLOB, or BFILE objects are valid in an AQ message. You can propagate these object types using AQ propagation with Oraclesince release 8.1.x. To enqueue an object type that has an LOB, you must first set the LOB_attribute to EMPTY_BLOB() and perform the enqueue. You can then select the LOB locator that was generated from the queue table's view and use the standard LOB operations. See the Oracle9i Application Developer's Guide - Large Objects (LOBs) for more information.

You can specify and modify the primary_instance and secondary_instance only in 8.1 compatible mode.

You cannot specify a secondary instance unless there is a primary instance.

When a queue, queue table, or subscriber is created, modified, or dropped, and if GLOBAL_TOPIC_ENABLED = TRUE, a corresponding LDAP entry is also created.