ORA-25228 Timeout or End-of-Fetch Error When Dequeuing Messages
(Doc ID 118781.1)
Last updated on JANUARY 10, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 8.1.7 to 11.2]
Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Messages have been enqueued and dequeued messages successfully from a queue within the same session.
The no_wait option has been specifie as a dequeue option.
Subsequent dequeues of messages which are enqueued from the same session return the error:
ORA-25228 "timeout or end-of-fetch during message dequeue from <USER>.<QUEUE_NAME>"
The following query reveals that messages are in the ready state for the queue:
select distinct msg_state from <USER>.aq$<QUEUE_TABLE_NAME> where queue = '<QUEUE_NAME>';
where <QUEUE_TABLE_NAME> is the queue table associated with the <QUEUE_NAME> (dba_queues).
Logging into another session as the same user and the dequeue succeeds without error.
The same error is reported whether you use a multiple or single-consumer queue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document