Re: SQL_FULLTEXT

Do you have any clues that v$sqlarea is less efficient than v$sqlstats. It clearly used to be several versions ago because it's execution indicated aggregation of v$sql, but of many years it has been an "indexed" access path to a single row in a separate x$ structure.

In both cases (v$sqlstats and v$sqlarea) the view content is dynamically constructed in the user memory, so they are both doing something to track through components that make up x$kglob, so one would hope that they can be as efficient as each other. If there is a distinct difference in performance then you could consider querying x$kglob directly.

(You can only get the first 32765 characters if it's a really long statement).

Regards
Jonathan Lewis

On Fri, 12 May 2023 at 08:43, Nenad Noveljic <nenad.noveljic_at_gmail.com> wrote:

> What's the least disruptive view to query to obtain the full SQL text?
>
> It should be V$SQLSTATS, but unfortunately V$SQLSTATS.SQL_FULLTEXT doesn't
> contain the full text. The support note "V$SQLSTATS.SQL_FULLTEXT does not
> show full of sql statements (Doc ID 2398100.1)" advises querying V$SQLAREA
> instead of V$SQLSTATS.
>
> Best regards,
> Nenad
>

--
http://www.freelists.org/webpage/oracle-l