Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: v$parameter

Re: v$parameter

From: Roger Snowden <snowden_at_NOT.com>
Date: Tue, 22 Dec 1998 02:23:29 GMT
Message-ID: <367F01CC.90C5FB4@NOT.com>


Microsoftitis? Yuchh! I'm not sure what that means, but it certainly doesn't sound pretty. My employment with Oracle notwithstanding, I personally find the product line quite consistent. The role/stored procedure thing works that way for some very good reasons. The access you have that seems inconsistent ought to be investigated. You may find that there are explicit grants you are not aware of.

Roger

Roger Snowden
Sr. Systems Engineering Specialist
Oracle Corporation
rsnowden_at_NOTus.oracle.com <-- to reply, remove the obvious

Nuno Souto wrote:
>
> That may be so. But I've found that not all role access is suspended. I've got
> stored procedures that are quite happy with access to other schema tables. But
> when I add a reference to a sequence, the role fails.
>
> I wish the whole thing would be consistent. That used to be one of the great
> things with ORACLE. Nowadays, it seems they have caught Microsoftitis...
>
> --
> Cheers
> Nuno Souto
> nsouto_at_acay.com.au
> Roger Snowden wrote in message <367BF7DC.D5BD1DBD_at_NOT.com>...
> >
> >Access to this sys-owned view was probably granted via a role. Roles are
> >suspended during stored procedure execution under the current releases.
> >To fix this, log in as sys and explicitly grant select on this view to
> >the procedure owner.
Received on Mon Dec 21 1998 - 20:23:29 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US