ORA-25254: time-out in LISTEN while waiting for a message

ORA-25254: time-out in LISTEN while waiting for a message

Cause: The specified wait time has elapsed and there were no messages for any of the agents in the agent-list.

Action: Try the LISTEN call with an appropriate time-out.

ORA-25253: listen failed, queue string.string is not enabled for dequeue

ORA-25253: listen failed, queue string.string is not enabled for dequeue

Cause: An attempt was made to specify a queue that is not enabled for dequeue in a LISTEN call.

Action: Enable the queue for dequeue using START_QUEUE, and retry the LISTEN call.

ORA-25252: listen failed, the address string is a non-persistent queue

ORA-25252: listen failed, the address string is a non-persistent queue

Cause: A non-persistent queue was specified as an address for an agent in the LISTEN call.

Action: Specify a normal queue as address for the agent, and retry the the LISTEN call.

ORA-25251: exceeded maximum number of recipients for message

ORA-25251: exceeded maximum number of recipients for message

Cause: An attempt was made to issue an ENQUEUE call that exceeded the the maximum number (1024) of recipients per message.

Action: Reduce the number of recipients to 1024 or less, and retry the call.

ORA-25250: Cannot specify a remote recipient for the message

ORA-25250: Cannot specify a remote recipient for the message

Cause: A recipient for the message enqueued to a non-persistent queue had a non-local address.

Action: Do not specify the address field or specify the queue which is the target of the enqueue

ORA-25249: dequeue failed, dequeue not allowed for queue string.string

ORA-25249: dequeue failed, dequeue not allowed for queue string.string

Cause: An attempt was made to dequeue from a non-persistent queue.

Action: Dequeue from a different queue.

ORA-25248: duplicate agent specified in the agent list

ORA-25248: duplicate agent specified in the agent list

Cause: An agent was specified more than once in the agent list of the LISTEN call.

Action: Remove the duplicate agent specification(s), and retry the call.

ORA-25247: %s is not a recipient of specified message

ORA-25247: %s is not a recipient of specified message

Cause: The consumer name specified in the dequeue options is not a recipient of the message specified by the message id.

Action: Ensure that the agent specified by the consumer name is a recipient of the message specified by the message id.

ORA-25246: listen failed, the address string is an 8.0 style exception queue

ORA-25246: listen failed, the address string is an 8.0 style exception queue

Cause: An 8.0 style exception queue was specified in the agent-list for the LISTEN call.

Action: Specify a normal 8.0 style queue or an 8.1 style queue in the agent-list.

ORA-25245: agent name cannot be specified if address is a single-consumer queue or an exception queue

ORA-25245: agent name cannot be specified if address is a single-consumer queue or an exception queue

Cause: The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue.

Action: Do not specify the agent name.

ORA-25244: dequeue index key not found, QUEUE string, rowid string

ORA-25244: dequeue index key not found, QUEUE string, rowid string

Cause: An internal error was encountered. There may be an inconsistency in the queue table index.

Action: Contact your Oracle customer support representative. You may need to provide the trace file and information about reproducing the error.

ORA-25243: CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string

ORA-25243: CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string

Cause: An attempt was made to dequeue from an exception queue by specifying the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when dequeuing from a normal queue created for multiple consumers.

Action: Specify only the message id in the dequeue options to dequeue a message from an exception queue.

ORA-25242: cannot change subscriber name from string to string without FIRST_ MESSAGE option

ORA-25242: cannot change subscriber name from string to string without FIRST_ MESSAGE option

Cause: An attempt was made to change the subscriber name while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.

Action: To use a subscriber name that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.

ORA-25241: cannot change correlation ID from string to string without FIRST_ MESSAGE option

ORA-25241: cannot change correlation ID from string to string without FIRST_ MESSAGE option

Cause: An attempt was made to change the correlation ID while using the NEXT_ MESSAGE or NEXT_TRANSACTION option for dequeuing.

Action: To use a correlation ID that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.

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

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

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

Action: To dequeue a message, specify a message ID or a dequeue condition or 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 dequeue condition or correlation ID in the dequeue options.

ORA-25239: message ID not supplied when dequeuing from exception queue string.string

ORA-25239: message ID not supplied when dequeuing from exception queue string.string

Cause: An attempt was made to dequeue from a release 8.0-compatible 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 supply a message ID when dequeuing from a release 8.0-compatible exception queue. Otherwise, upgrade the queue_table containing the queue to release 8.1-compatible using the DBMS_ AQADM.MIGRATE_QUEUE_TABLE procedure.

ORA-25238: too many recipients specified for message destination string

ORA-25238: too many recipients specified for message destination string

Cause: An ENQUEUE was performed with more than 32 recipients for the given destination (address).

Action: Reduce the number of recipients to 32 or less, and retry the call.

ORA-25237: navigation option used out of sequence

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-25236: buffer too small for user data

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-25235: fetched all messages in current transaction

ORA-25235: fetched all messages in current transaction

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

Action: Use the NEXT_TRANSACTION navigation option to move to the next also use the FIRST_MESSAGE option to start from the head of the queue again.

ORA-25234: NEXT_TRANSACTION navigation option invalid for queue table string.string

ORA-25234: NEXT_TRANSACTION navigation option invalid for queue table string.string

Cause: The NEXT_TRANSACTION navigation option 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-25233: invalid parameter specified for NAVIGATION

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 the first message that satisifies the criterion, NEXT_MESSAGE for dequeuing the next message that satisifies the criterion and NEXT_TRANSACTION for moving to a set of messages enqueued by another transaction.

ORA-25232: duplicate recipients specified for message

ORA-25232: duplicate recipients specified for message

Cause: An enqueue was performed with duplicate queue agents in the recipients parameter.

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

ORA-25231: cannot dequeue because CONSUMER_NAME not specified

ORA-25231: cannot dequeue because CONSUMER_NAME not specified

Cause: A user tried to dequeue from a queue that has been created for multiple consumers but a CONSUMER_NAME was not been specified in the dequeue options.

Action: Specify the CONSUMER_NAME in the dequeue options.

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

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

Cause: A negative value has been specified for WAIT.

Action: specify a non negative value or FOREVER.

ORA-25229: error on transformation of message string string

ORA-25229: error on transformation of message string string

Cause: There was an error when transforming a message at enqueue, dequeue or propagation time.

Action: Correct the transformation function.

ORA-25228: timeout or end-of-fetch during message dequeue from string.string

ORA-25228: timeout or end-of-fetch during message dequeue from string.string

Cause: User-specified dequeue wait time has passed or the end of the queue has been reached but no message has been retrieved.

Action: Try dequeue again with the appropriate WAIT_TIME or the FIRST_ MESSAGE option.

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

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

Cause: The queue has not been enabled for dequeue.

Action: Enable the queue using START_QUEUE.

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

ORA-25225: invalid value string, 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-25224: sender name must be specified for enqueue into secure queues

ORA-25224: sender name must be specified for enqueue into secure queues

Cause: An attempt was made to enqueue into a secure queue without specifying a sender name.

Action: Enqueue the message with sender name specified.

ORA-25223: user_data type used is not supported

ORA-25223: user_data type used is not supported

Cause: An attempt was made to enqueue data into a non persistent queue that is of a type other than the supported raw or object type.

Action: Enqueue the message again with data of raw or object type.

ORA-25222: enqueue failed, complete sender info. not provided for a queue supporting non-repudiation

ORA-25222: enqueue failed, complete sender info. not provided for a queue supporting non-repudiation

Cause: An attempt was made to enqueue to a queue without giving the complete sender information (name) for a queue supporting non-repudiation

Action: Provide the sender information

ORA-25221: enqueue failed, signature specified queue not supporting non-repudiation

ORA-25221: enqueue failed, signature specified queue not supporting non-repudiation

Cause: An attempt was made to enqueue to a queue specifying the signature for a queue not supporting non-repudiation

Action: Remove the signature

ORA-25220: enqueue failed, signature not specified for a non-repudiable queue

ORA-25220: enqueue failed, signature not specified for a non-repudiable queue

Cause: An attempt was made to enqueue to a non-repudiable queue without specifying the signature

Action: Give the signature

ORA-25219: enqueue failed, sequence deviation not allowed for queue string.string

ORA-25219: enqueue failed, sequence deviation not allowed for queue string.string

Cause: An attempt was made to enqueue to a non-persistent queue with sequence deviation specified.

Action: Do not specify sequence deviation.

ORA-25218: enqueue failed, delay must be zero for queue string.string

ORA-25218: enqueue failed, delay must be zero for queue string.string

Cause: An attempt was made to enqueue to a non-persistent queue with delay greater than zero seconds.

Action: Set delay to zero.

ORA-25217: enqueue failed, visibility must be IMMEDIATE for queue string.string

ORA-25217: enqueue failed, visibility must be IMMEDIATE for queue string.string

Cause: An attempt was made to enqueue to a non-persistent queue without setting visibility to IMMEDIATE.

Action: Set visibility to IMMEDIATE.

ORA-25216: invalid recipient, either NAME or ADDRESS must be specified

ORA-25216: invalid recipient, either NAME or ADDRESS must be specified

Cause: Both attributes, NAME and ADDRESS, were specified null for one of the recipients in the recipient list.

Action: Specify a non-null NAME or ADDRESS for the recipient.

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

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

Cause: A user tries 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-25214: cannot specify delay or expiration for enqueue to exception queue

ORA-25214: cannot specify delay or expiration for enqueue to exception queue

Cause: A message was enqueued to the exception queue with either delay or expiration specified.

Action: Enqueue a message without delay or expiration.

ORA-25213: message with specified RELATIVE_MSGID has been dequeued

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: none

ORA-25212: invalid PRIORITY specified when using sequence deviation

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-25211: invalid DELAY specified when using sequence deviation

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-25210: invalid value for RELATIVE_MSGID, no message in queue with that msgid

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-25209: invalid value string, EXPIRATION should be non-negative or NEVER

ORA-25209: invalid value string, EXPIRATION should be 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-25208: RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE

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: Either specify an existing relative message identifier or don t specify sequence deviation as BEFORE.

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

ORA-25207: enqueue failed, queue string.string 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-25206: enqueue failed, enqueue to exception queue string.string not permitted

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

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

Action: Try enqueueing to another queue.

ORA-25205: the QUEUE string.string does not exist

ORA-25205: the QUEUE string.string does not exist

Cause: The specified queue does not exist.

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

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

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-25203: invalid value string, DELAY should be non-negative

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

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

Action: Specify a non negative integer for DELAY.

ORA-25202: invalid value NULL, string should be non-NULL

ORA-25202: invalid value NULL, string should be non-NULL

Cause: A NULL value was specified for the parameter.

Action: Specify a non-NULL value.

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

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-25200: invalid value string, QUEUE_NAME should be (SCHEMA.(NAME

ORA-25200: invalid value string, QUEUE_NAME should be (SCHEMA.(NAME

Cause: A NULL parameter was specified for QUEUE_NAME.

Action: Specify a non-NULL queue name.

ORA-25199: partitioning key of a index-organized table must be a subset of the primary key

ORA-25199: partitioning key of a index-organized table must be a subset of the primary key

Cause: An attempt to specify a partitioning key which is not a prefix of the primary key of the index-organized table

Action: Select a different partitioning key

ORA-25198: only range, list, and hash partitioning are supported for index-organized table

ORA-25198: only range, list, and hash partitioning are supported for index-organized table

Cause: System, or Composite partitioning schemes are not supported yet

Action: Select a different partitioning scheme

ORA-25197: an overflow segment already exists for the indexed-organized table

ORA-25197: an overflow segment already exists for the indexed-organized table

Cause: An attempt was made to ADD OVERFLOW segment on an index-organized table that already has an overflow segment

Action: none

ORA-25196: keyword MOVE in ALTER TABLE MOVE must immediately follow lamp;lt;lamp;nbsp;table namelamp;gt;

ORA-25196: keyword MOVE in ALTER TABLE MOVE must immediately follow lamp;lt;lamp;nbsp;table namelamp;gt;

Cause: MOVE specified after one or more other ALTER options

Action: Remove the illegal option(s)

ORA-25195: invalid option for index on an index-organized table

ORA-25195: invalid option for index on an index-organized table

Cause: An attempt to specify one or more of the following options for index on an IOT: BITMAP, REVERSE, PCTUSED

Action: none

ORA-25194: invalid COMPRESS prefix length value

ORA-25194: invalid COMPRESS prefix length value

Cause: The specified value must be a positive integer less than the number of key columns

Action: Specify an appropriate value.