Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!
Course Of The Month
9 days, 15 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Oracle read only user
Posted on 2016-10-17
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.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4
7 Comments
Active today
select any table - this will apply to non-sys owned tables and views
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.
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.
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 .
Active today
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)
Active 1 day ago
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.
Active today
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
Featured Post
Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Note: this article covers simple compression. Oracle introduced in version 11g release 2 a new feature called Advanced Compression which is not covered here.
General principle of Oracle compression
Oracle compression is a way of reducing the d…
Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
This video explains at a high level with the mandatory Oracle Memory processes are as well as touching on some of the more common optional ones.
Via a live example, show how to take different types of Oracle backups using RMAN.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month9 days, 15 hours left to enroll
Earn Certification
Certified Information Systems Auditor (CISA)
$99.00$89.10
624 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.