Oracle9i Supplied PL/SQL Packages and Types Reference Release 1 (9.0.1) Part Number A89852-02 |
|
DBMS_AQADM , 2 of 31
This procedure creates a queue table for messages of a predefined type. The sort keys for dequeue ordering, if any, must be defined at table creation time. The following objects are created at this time:
aq$_<queue_table_name>_e
.
aq$<queue_table_name>
.
aq$_<queue_table_name>_t
.
aq$_<queue_table_name>_i
.
For Oracle8i-compatible queue tables, the following two index organized tables are created:
aq$_<queue_table_name>_s
. This table stores information about the subscribers.
aq$_<queue_table_name>_r
. This table stores information about rules on subscriptions.
aq$_<queue_table_name>_h
. This table stores the dequeue history data.
DBMS_AQADM.CREATE_QUEUE_TABLE ( queue_table IN VARCHAR2, queue_payload_type IN VARCHAR2, storage_clause IN VARCHAR2 DEFAULT NULL, sort_list IN VARCHAR2 DEFAULT NULL, multiple_consumers IN BOOLEAN DEFAULT FALSE, message_grouping IN BINARY_INTEGER DEFAULT NONE, comment IN VARCHAR2 DEFAULT NULL, auto_commit IN BOOLEAN DEFAULT TRUE, primary_instance IN BINARY_INTEGER DEFAULT 0, secondary_instance IN BINARY_INTEGER DEFAULT 0, compatible IN VARCHAR2 DEFAULT NULL);
Parameter | Description |
---|---|
queue_table |
Name of a queue table to be created. |
queue_payload_type |
Type of the user data stored. See "Type Name" for valid values for this parameter. |
storage_clause |
The storage parameter is included in the If a tablespace is not specified here, then the queue table and all its related objects are created in the default user tablespace. If a tablespace is specified here, then the queue table and all its related objects are created in the tablespace specified in the storage clause. See Oracle9i SQL Reference for the usage of these parameters. |
sort_list |
The columns to be used as the sort key in ascending order.
'<
The allowed column names are After a queue table is created with a specific ordering mechanism, all queues in the queue table inherit the same defaults. The order of a queue table cannot be altered after the queue table has been created. If no sort list is specified, then all the queues in this queue table are sorted by the enqueue time in ascending order. This order is equivalent to FIFO order.
Even with the default ordering defined, a dequeuer is allowed to choose a message to dequeue by specifying its |
multiple_consumers |
|
message_grouping |
Message grouping behavior for queues created in the table.
|
comment |
User-specified description of the queue table. This user comment is added to the queue catalog. |
auto_commit |
Note: This parameter has been deprecated. |
primary_instance |
The primary owner of the queue table. Queue monitor scheduling and propagation for the queues in the queue table are done in this instance. The default value for primary instance is 0, which means queue monitor scheduling and propagation will be done in any available instance. |
secondary_instance |
The queue table fails over to the secondary instance if the primary instance is not available. The default value is 0, which means that the queue table will fail over to any available instance. |
compatible |
The lowest database version with which the queue is compatible. Currently the possible values are either'8.0' or '8.1'. |
CLOB
, BLOB
, and BFILE
are valid attributes for AQ object type payloads. However, only CLOB
and BLOB
can be propagated using AQ propagation in Oracle8i release 8.1.5 or later. See the Oracle9i Application Developer's Guide - Advanced Queuing for more information.
The default value of the compatible parameter depends on the database compatibility mode in the init.ora
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.
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|