Thanks in Advance
James
select value from v$system_parameter where name='user_dump_dest';
I think you need to be logged in as sys or system... Or with DBA privs,
something like that
"Gabriel Gonzalez" <no-...@no-spam.com> wrote in message
news:7oGcnTKpA7A...@giganews.com...
>select value from v$system_parameter where name='user_dump_dest';
>
>I think you need to be logged in as sys or system... Or with DBA privs,
>something like that
>
The SELECT_CATALOG_ROLE is sufficient.
Sybrand Bakker, Senior Oracle DBA
To reply remove -verwijderdit from my e-mail address
Ah, thanks... The last time I did this I was in a big hurry, and paid no
attention.
A direct grant to v_$parameter should work as well, if you don't want to
give the entire select_catalog_role to a user.. having access to v$sqltext
etc.. views is a potential security hole for example..
Tanel.
"Gabriel Gonzalez" <no-...@no-spam.com> wrote in message
news:VtWdnRZO8JL...@giganews.com...
>A direct grant to v_$parameter should work as well, if you don't want to
>give the entire select_catalog_role to a user.. having access to v$sqltext
>etc.. views is a potential security hole for example..
>
>Tanel.
A direct grant to v_$parameter will be LOST upon export, because SYS
isn't exported. It will consequently create an administration
nightmare, and I would consider unknown individuals having access
directly to an unknown set of v$ views definitely MUCH MORE of a
security loophole compared to using the SELECT_CATALOG_ROLE.
Anyway, you're nitpicking: most 3rd party sw, developed by juniors,
grants the DBA role by design to every individual user, and forgets to
assign an appropiate password to those users.
But, yes, we are lucky if people even change the system & sys password. For
example, even I don't always do it :|
Tanel.