If Deq_condition Is Used, Session Memory Keeps Growing.
(Doc ID 729631.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.1.0.7 [Release 11.1]
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.
Symptoms
PGA Memory can be exhausted by a process when dequeue is being performed with a dequeue condition.
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.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |