Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 25200-25699: Advanced Query Messages

For more messages on advanced query, see "24000-24099: Administrative Interface for Advanced Query Messages" on page 2¬335.

##### ORA-25200: invalid value name.name QUEUE_NAME should be [SCHEMA.]NAME

Cause: A NULL parameter was specified for the queue name.

Action: Specify a NON-NULL queue name.

##### ORA-25201: invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE

Cause: An invalid value specified for parameter VISIBILITY.

Action: Specify either ON_COMMIT or IMMEDIATE.

##### ORA-25202: invalid value NULL, name should be non-NULL

Cause: A NULL value was specified for the parameter.

Action: Specify a non-NULL value.

##### ORA-25203: invalid value num, DELAY should be non-negative

Cause: A negative value or NULL was specified for DELAY.

Action: Specify a non negative integer for DELAY.

##### ORA-25204: invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP

Cause: An invalid SEQUENCE_DEVIATION was specified.

Action: Specify either the option BEFORE or TOP.

##### ORA-25205: the QUEUE name.name does not exist

Cause: The specified queue does not exist.

Action: Create the queue first before specifying it for enqueue or dequeue.

##### ORA-25206: enqueue failed, enqueue to exception queue name.name not permitted

Cause: An attempt was made to enqueue to an exception queue.

Action: Try enqueueing to another queue.

##### ORA-25207: enqueue failed, queue name.name is disabled from enqueueing

Cause: The queue has been stopped to prevent any further enqueueing.

Action: Enable the queue first by using an administrative operation.

##### ORA-25208: RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE

Cause: A relative message identifier should be specified if sequence deviation is specified as BEFORE.

Action: Specify a non-null parameter for sequence deviation. valid values are either A, B, or T.

##### ORA-25209: invalid value num, EXPIRATION should non-negative or NEVER

Cause: The expiration is less than zero or NULL.

Action: Specify a valid value for expire_after which should be greater than or equal to zero or NEVER.

##### ORA-25210: invalid value for RELATIVE_MSGID, no message in queue with that msgid

Cause: No message inm the queue with the msgid equal to the specified RELATIVE_MSGID.

Action: Try again with a valid RELATIVE_MSGID.

##### ORA-25211: invalid DELAY specified when using sequence deviation

Cause: The DELAY specified in the enqueue is greater than the delay of the message with the given relative message id.

Action: Set the DELAY to be less than or equal to the delay of the message with the given relative message id. If the TOP option is used the delay must be less than or equal to the delay of all the messages in the queue.

##### ORA-25212: invalid PRIORITY specified when using sequence deviation

Cause: The PRIORITY specified in the enqueue is less than the priority of the message with the given relative message id.

Action: Set the PRIORITY to be less than the delay of the message with the given relative message id. If the TOP option is used the prioirty must be greater than or equal to the priority of all the messages in the queue.

##### ORA-25213: message with specified RELATIVE_MSGID has been dequeued

Cause: The message specified by the RELATIVE_MSGID field in the sequence deviation BEFORE option has been dequeued.

Action: No action required. This is an informational message only.

##### ORA-25215: user_data type and queue type do not match

Cause: An attempt was made to enqueue an object to a queue that was created for objects of different type.

Action: Try enqueue again with an object of the right type.

##### ORA-25225: invalid value name, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED

Cause: An invalid parameter has been specified for DEQUEUE_MODE.

Action: Specify either REMOVE, BROWSE or LOCKED.

##### ORA-25226: dequeue failed, queue name.name is not enabled for dequeue

Cause: The queue has not been enabled for dequeue.

Action: Enable the queue using START_QUEUE.

##### ORA-25228: timeout in dequeue from name.name while waiting for a message

Cause: User-specified dequeue wait time has passed but no message has been retrieved.

Action: Try dequeue again with the appropriate WAIT_TIME.

##### ORA-25230: invalid value name, WAIT should be non-negative

Cause: A negative value was specified for WAIT.

Action: Specify a non negative value or FOREVER.

##### ORA-25231: SUBSCRIBER not specified

Cause: An attempt was made to dequeue from a queue that has been created for subscription but a subsciber has not been specified.

Action: Try dequeue again after specifying the name of the subscriber.

##### ORA-25232: duplicate recipients specified for message

Cause: An enqueue was performed with duplicate queue agents in the recipient's parameter.

Action: Remove the duplicate queue agent and retry the call.

##### ORA-25233: invalid parameter specified for NAVIGATION

Cause: An invalid parameter has been specified for NAVIGATION.

Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE, or NEXT_TRANSACTION. Use FIRST_MESSAGE for dequeuing first message that satisifies the criterion, NEXT_MESSAGE for dequeuing next message that satisifies the criterion and NEXT_TRANSACTION for moving to a set of messages enqueued by another transaction.

##### ORA-25234: NEXT_TRANSACTION navigation option invalid for queue table basename.extension

Cause: The NEXT_TRANSACTION navigation flag was used in a dequeue from a queue in a queue table that was not created for transactional grouping.

Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation option. If you want to dequeue messages using transactional grouping create the queue in a queue table that has transactional grouping enabled.

##### ORA-25235: fetched all messages in current transaction

Cause: The NEXT_TRANSACTION navigation option was used in a dequeue where there were no messages that belong to the same transaction.

Action: Use the NEXT_TRANSACTION navigation option to move to the next group of messages that belong to the same transaction. You can also use the FIRST_MESSAGE option to start from the head of the queue again.

##### ORA-25236: buffer too small for user data

Cause: The variable or buffer used for the out parameter payload is too small for the user data dequeued.

Action: Increase the size of the buffer or the size of the variable. Maximum size allowed is 32K.

##### ORA-25237: navigation option used out of sequence

Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after dequeuing all the messages.

Action: Reset the dequeuing position using the FIRST_MESSAGE naviagtion option and then specify the NEXT_MESSAGE or NEXT_TRANSACTION option.

##### ORA-25238: too many recipients specified for message

Cause: An enqueue was performed with more than 32 recipients.

Action: Redcue the number of recipients to 32 and retry the call.

##### ORA-25239: message ID not supplied when dequeueing from exception queue name.name

Cause: An attempt was made to dequeue from an exception queue without including a message ID in the dequeue options.

Action: Check the application to ensure that the queue name has been specified correctly. If the queue name is correct, then supply a message ID when dequeueing from the exception queue.

##### ORA-25240: message ID and correlation ID specified in dequeue options

Cause: An attempt was made to dequeue by including both a message ID and a correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either a message ID, correlation ID, or neither ID.

Action: To dequeue a message, specify a message ID or a correlation ID in the dequeue options, but do not specify both. If you want to dequeue in the queue's sort order, then do not specify either the message ID or correlation ID in the dequeue options.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index