If Deq_condition Is Used, Session Memory Keeps Growing.
Last updated on SEPTEMBER 06, 2010
Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 - Release: 10.2 to 10.2
Oracle Server - Enterprise Edition - Version: 220.127.116.11 to 18.104.22.168 [Release: 11.1 to 11.1]
Information in this document applies to any platform.
Checked for currency 06-Sep-10
Every dequeuing condition generates a different statement of the following form, with a different
correlation id per message:
select tab.row_id, ... from "MGWUSER"."AQ$_<QUEUE_TABLE>_F" tab
where q_name = :1 and (state = :2 ) and (UTL_RAW.CAST_TO_VARCHAR2(tab.user_data.correlationId) = '5405539335940739')
the memory associated with this is not released until the dequeueing session ends.
The open_cursors parameter is set to a large value.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms