Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
For more messages on advanced query, see "24000-24099: Administrative Interface for Advanced Query Messages" on page 2¬335.
Cause: A NULL parameter was specified for the queue name.
Action: Specify a NON-NULL queue name.
Cause: An invalid value specified for parameter VISIBILITY.
Action: Specify either ON_COMMIT or IMMEDIATE.
Cause: A NULL value was specified for the parameter.
Action: Specify a non-NULL value.
Cause: A negative value or NULL was specified for DELAY.
Action: Specify a non negative integer for DELAY.
Cause: An invalid SEQUENCE_DEVIATION was specified.
Action: Specify either the option BEFORE or TOP.
Cause: The specified queue does not exist.
Action: Create the queue first before specifying it for enqueue or dequeue.
Cause: An attempt was made to enqueue to an exception queue.
Action: Try enqueueing to another queue.
Cause: The queue has been stopped to prevent any further enqueueing.
Action: Enable the queue first by using an administrative operation.
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.
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.
Cause: No message inm the queue with the msgid equal to the specified RELATIVE_MSGID.
Action: Try again with a valid RELATIVE_MSGID.
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.
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.
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.
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.
Cause: An invalid parameter has been specified for DEQUEUE_MODE.
Action: Specify either REMOVE, BROWSE or LOCKED.
Cause: The queue has not been enabled for dequeue.
Action: Enable the queue using START_QUEUE.
Cause: User-specified dequeue wait time has passed but no message has been retrieved.
Action: Try dequeue again with the appropriate WAIT_TIME.
Cause: A negative value was specified for WAIT.
Action: Specify a non negative value or FOREVER.
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.
Cause: An enqueue was performed with duplicate queue agents in the recipient's parameter.
Action: Remove the duplicate queue agent and retry the call.
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.
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.
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.
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.
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.
Cause: An enqueue was performed with more than 32 recipients.
Action: Redcue the number of recipients to 32 and retry the call.
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.
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.