RE: Feedback on query for monitoring index usage in 9i

metalink Note:160712.1 does much the same thing (it just takes the clause
"where io.owner# = userenv('SCHEMAID')" out of the definition of
v$object_usage to create a new view that is no longer restricted to the
current schema).

Now that we've upgraded to 9.2.0.5.0, I'm looking to see which indexes =
are not being used over time, thanks to the new feature. Trying to =
monitor this is a pain using the V$OBJECT_USAGE view (which itself is an =
oddity -- where's the V_$?) because it'll only show indexes in the =
current schema that are already being monitored. I'd like to see =
indexes for the whole DB so I can see which ones are not being monitored =
as well. So I came up with this SQueaL, based on V$OBJECT_USAGE: