Re: interpreting v$sort_usage output

Hi!

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:bmph5u$7qa$1$8300dec7_at_news.demon.co.uk...
>
> The first problem is that Oracle made a mistake
> when defining v$sort_usage - there is a real column
> called USER, but this is a word reserved for a
> 'pseudo-column', so whoever queries v$sort_usage
> will see their username as the only person using
> temp space.

Yep, this has been problem with v$sort_usage, but gv$sort_usage works ok, it selects username from v$session as it should. And in latest releases (9.2.0.4 for example), both user and username columns show correct results since v$sort_usage selects for "USER" instead of USER from gv$sort_usage.

The fun thing is, that even several of Oracle's DBA training materials described this behaviour like it was something "very internal" or intended behaviour that user column has wrong contents...

Tanel. Received on Sat Oct 25 2003 - 07:04:10 CDT