Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Oracle read only user
I need to create database user that should be able to view all the database objects - tables, procedures, packages, functions and triggers.
I can say - grant select any table to user. How do I go about doing this for the other objects.
I can say - grant select any table to user. How do I go about doing this for the other objects.
Who is Participating?
Thanks LVL73. If you grant select any dictionary, can I go and view the package body from Packagaes in sql developer or can I only view them from the dba_source table .
lvl73 isn't a name, it's a counter (sort of) indicating the amount of time spent on EE answering questions.
but, I assume you meant me, sdstuber
sql developer uses the ALL_* views, but if you have select any dictionary, that should make ALL_* act pretty much like DBA_* (except a little heavier because the ALL_* views are doing extra work to confirm permissions)
but, I assume you meant me, sdstuber
sql developer uses the ALL_* views, but if you have select any dictionary, that should make ALL_* act pretty much like DBA_* (except a little heavier because the ALL_* views are doing extra work to confirm permissions)
Yes, "select ANY" will get you what you need but it will probably also get you a whole lot more.
You should really follow good security practices:
https://en.wikipedia.org/wiki/Principle_of_least_privilege
Select any dictionary and table can be a security issue. It doesn't limit what the user can see.
If you want them to see absolutely everything in the database in every schema, even the sys and system schemas, then grant them.
You should really follow good security practices:
https://en.wikipedia.org/wiki/Principle_of_least_privilege
Select any dictionary and table can be a security issue. It doesn't limit what the user can see.
If you want them to see absolutely everything in the database in every schema, even the sys and system schemas, then grant them.
what is your db version?
if it's 12.1.0.2 or higher you should probably use "read any table" instead of "select any table"
the select privilege implicitly allows you to lock objects even if you can't update/insert/delete on them.
It's as simple as "select * from some_table for update"
even if you don't have update privilege, the select grant allows you to do that and that query would lock every row in the table.
if you have "read any table" privilege, you can't do that
if it's 12.1.0.2 or higher you should probably use "read any table" instead of "select any table"
the select privilege implicitly allows you to lock objects even if you can't update/insert/delete on them.
It's as simple as "select * from some_table for update"
even if you don't have update privilege, the select grant allows you to do that and that query would lock every row in the table.
if you have "read any table" privilege, you can't do that
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month6 days, 11 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
select any dictionary - this will apply to sys owned tables and views.
For 12c it does NOT include SYS.USER$ (and others), you will need to grant select on that directly, but there is usually no need to do that and is not recommended.
for procedures, pacakges, functions and triggers I assume you mean you want to view the source.
with select any dictionary you can read dba_source for all of those
if you are trying to read the code by behind wrapped objects, you can't. There is no privilege that allows that, not even SYS has that authority.