Unusually High Value In V$UNDOSTAT.MAXQUERYLEN For Short Recursive SQL Statements
(Doc ID 2776001.1)
Last updated on MARCH 24, 2022
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124.0 and later
Oracle Database - Standard Edition - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Recursive SQL statements which should have completed in very short time appears as having high MAXQUERYLEN in V$UNDOSTAT.
Few examples of such recursive statements may include:
select /*+ no_parallel */ spare4 from sys.optstat_hist_control$ where sname=:1
select ts# from ts$ where ts$.online$ != 3 and bitand(flags,2048) != 2048
select 1 from sys.aq$_subscriber_table where rownum < 2 and subscriber_id <> 0 and table_objno <> 0
Another symptom may be that these statements show up in V$OPEN_CURSOR for a long time.
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