Re: V$ tables

From: Loadrunner <load_at_runner.com>
Date: Fri, 14 Jun 2002 14:35:22 +0100
Message-ID: <1024061570.7355.0.nnrp-14.c2d92da9@news.demon.co.uk>

I did work once on a site as a developer and I could not have access to the v$ tables and this was on our development servers. Get this, they wouldn't even allow a plan_table to created and used.

Only reason I guess is that the DBA's wanted to feel superior, sort of this is my ball and you can't play with it. A sort of "We are the Oracle masters and you developers are scum" attitude.

Needless to say I wrote some dodgy SQL and got the DBA's to spend some of their own time sort it out.

"Charlie Edwards" <Charlie3101_at_hotmail.com> wrote in message news:db479d88.0206140441.584fe727_at_posting.google.com...
> Hi,
>
> I would be grateful for a DBA's opinion on this ...
> Which V$ tables should be available to developers as a matter of
> course?
>
> v$process, v$session, v$lock, v$sqlarea, v$sqltext, v$locked_object,
> v$session_longops ...
>
> Any others?
>
> For that matter, is there any reason why developers should not have
> acess to ALL V$ tables in a development environment?
>
> Thanks,
>
> CE
Received on Fri Jun 14 2002 - 08:35:22 CDT