Restricted view access to other schemas 'showstopper' problem

I'm tasked with the potential roll-out of SQL Developer across a large number of users (doing away with equivalent software in the process).
The feedback has been very positive. However, the only real issue stopping the replacement from progressing is that we cannot view certain objects in other schemas (package bodies, triggers etc) ... i.e. we need to connect as the schema owner to view these. This is essential, otherwise everyone would need to know the application schemas password.
Our current software has the same issue unless the following option in the Options/Startup window is activated: 'Check for access to DBA views. Otherwise, SYS.ALL_xx views will be used when listing objects'. Thereafter the issue is resolved.
Is there any workaround (e.g. like the above) in SQL Developer?
Many Thanks.

Sue, thanks for your reply although I already have access to Package code via tools like SQL*Plus.
I guess the problem being discussed here is similar to the following thread (for which you have already logged a bug). See:
How do I view package bodies in another schema ?
Re: How do I view package bodies in another schema ?
On a similar issue, I note that there is a possibility that a fix will indeed be implemented in release 1.1. See:
Package body not visible
Re: Package body not visible
Please advise what the current status is relating to a fix?
Many thanks for any clarification.

Similar Messages

Queue available in one schema want to access through other schema

Hi All,
There is one queue available in apps schema. I want to access the queue from other schema. Can anyone provide me the steps.
Regards

select * from schema_name.table_name;
*you must have sufficient privileges to see this scheme

View packages in other schemas

Here is my scenario:
I'm a developer that needs read only access to production versions of packages for change control reasons. I have the following privs and roles:
select any table, select_catalog_role, select on dba_objects, select on dba_jobs, connect and create session.
In Toad I am able to choose the schema that owns the packages and they show up in the package tree. This does not happen in raptor. In Toad there is an option to use DBA_% views to populate the object tree. This option would be helpful in Raptor as the current query doesn't show the packages. For reference here is the query we got in the session trace:
SELECT OBJECT_NAME, OBJECT_TYPE, OBJECT_ID FROM SYS.ALL_OBJECTS WHERE OWNER = 'FOO' AND OBJECT_NAME LIKE '%' AND OBJECT_TYPE IN ('PACKAGE') AND SUBOBJECT_NAME IS NULL AND OBJECT_NAME NOT LIKE 'BIN$%'
Are there any workarounds to this, or can it be added to the new feature list for the next release?

I think it would be great if you could set an option to use the DBA_% views in the connection navigator instead of the ALL_% views (so long as you have access to them). However, from Enhancement request: Include DBA_% views when browsing this has already been logged as an enhancement.
As far as how things work at your site - I assume that the DBAs have granted you select access on some or all of the DBA views, rather than giving you DBA privs (ie select any table, etc).

Restrict view access to a distribution group

Hi, management have decided they want to have a distribution group made up of all employees personal email addresses (in case of emergency broadcasts etc etc).
I have been trying to figure out a way to create this list, but only give a few particular users access to view and send to it.
So far, my thinking is I can put the list into an OU, which only has permissions for those users to view, and disable it for everyone else.
Just wondering if there is a better way to do this? The send restrictions are pretty straight forward, its the view restrictions that need to be dealt with...
Thanks,
Nathan

Hi Nathan,
As Amit suggested, you can create a dynamic distribution group. And then follow the steps below to set the message delivery restrictions.
Open EMC -> Recipient Configuration -> Distribution Group -> right click the dynamic distribution group you want to configure -> Properties -> Mail Flow Settings -> double click the Message Delivery Restrictions -> specify the user who
can send to this distribution group.
For more information, here is a helpful article for your reference.
Configure Dynamic Distribution Group Properties
http://technet.microsoft.com/en-us/library/bb124560(v=exchg.141).aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Restricted/View Access Only - User

Hi,
I have a need to create a user account on our ASA (8.x code) device but only allow them read access; particularly, view the overall config and interface statistics.
I have tested with an account, but my attempts at setting the privilege level seem to be ineffective at restricting accesss. How might I accomplish this task?
thanks,
Jim

Jim, you should get it working after reference this thread.
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Security&topic=Firewalling&topicID=.ee6e1fa&fromOutline=true&CommCmd=MB?cmd=display_location&location=.2cc2c575/4
If still have issues let us know.
B.regards

Wwsec_api packaged procedures not accessed by other schema user.

I am trying to use wwsec_api packaged procedure in portal application developed in another users schema and owned by that user. When I try to execute wwsec_api procedures it gives numeric or value error.
could anyone tell what all permissions/grants to be set to access security package in other user's schema's portal application?

Have you tried running provsyns.sql? It's detailed in the PDK.

Restrict Opportunity access from other Org Unit Sales agent

Hello,
My Scenario is, there is different Organisation Units and Sales agents are assigned to those Org units. Now the issue is, Sales agent from one Org unit is looking into the opportunity of other Org unit. As the sales agents have their own targets and competition, one should not see the Opportunities of other Org unit.
How can we achieve this ?
a ) Can we achieve this through PFCG roles, if so how ?
b) I heard about the concept of Access control engine, which is usefull in this kind of scenario's. but again we need to implement ACS here, which I dont have ides.
Please suggest me the best method to achieve this. Also provide me step by step procedure also to achieve this.
Thanks,
MD.

Hi, madhusudan444.
Yes, you can achieve this by PFCG. Authorization objects CRM_ORD_LP or CRM_ORD_OE will help you.
For more information, please, follow to this link:
http://help.sap.com/saphelp_crm70/helpdata/EN/48/a44236ceb873e8e10000000a42189b/frameset.htm
I would not recommend using ACE in this issue, because ACE is abap. Your issue can achieve by standard procedure.

Inconsistent logic for viewing others schemes objects in browser

A while ago when we upgraded our db's to Oracle 10 we also replaced our famous green friend for Sql Developer with our entire development crew.
Among a few other things, people were not all that happy, seeing that they lost the desired "check for access to dba views option". But as long as we could rely on a consistent view in the "other schema" in all possible views (via table, or directly in the navigator) we could defend this way of thinking for not being able to see everything.
But unfortunately, in the latest version "1.5.1 5440", we still see inconsistent things...
for example :
via browser (other users schema)
=> Indexes are not visible in the indexes branch point, but they do show up on the indexes tab for the corresponding table.
=> For the same "other users scheme", Triggers do show up in the triggers branch point, but then when we check the trigger tab for the corresponding table, they are not shown
It looks like waiting for yet another version is no option and we will be forced to retreat to the green commercial swamp on high demand of our developers...
Ribbit :-(

There are still a few glitches in the queries used for certain things - I cannot remember the problem you mention with indexes being posted before (although I get the same problem with indexes visible in all_indexes not appearing on other users index node), but the trigger tab problem has been discussed before (1.5PROD/EA3/EA2/EA1: Only table owners triggers show in Table's trigger tab
theFurryOne

Syscontext use in a object by one schema can't access by others

Syscontext related one schema objects given error during access in othere schema and use to take
sys privs like "select any dictionary "
Grant create any context to HR;
conn hr/hr123 ;
then
CREATE OR REPLACE PROCEDURE "HR"."SET_ATT_DATE" (att_date IN DATE) AS
var_date VARCHAR2(30);
BEGIN
var_date:=TO_CHAR(att_date,'DD-MM-YYYY');
DBMS_SESSION.SET_CONTEXT('ATTENDANCE_CTX','ATT_DATE',var_date);
END;
create context ATTENDANCE_CTX using SET_ATT_DATE ;
Whenever THIS procedure name "HR.SET_ATT_DATE" is used by schema scott in program it is given
error insuficient priviledge during compilation but whenever i am given "select any dictionary to
scott " then it's getting compile
where as i have given grant priviledge
grant execute on HR.SET_ATT_DATE to scott.
Plz help me in this regards

Thanks very much Mylenium for your help - I've scoured the file looking for everything you mention, and there anything fancy at all. I'm using no time-stretching or remapping, simply putting a text layer on top of a video, and moving its in and out points. No blurs or odd keyframes as far as I can tell. Video and comp are both 29.97 framerate (comp created using "New comp from selection").
Glen

Create user with DBA privileges with a restriction to access user data

Hi
I need to create a user with all DBA privileges with a restriction to access all user schemas
Thanks,
Balaji

Use Database Vault - http://download.oracle.com/docs/cd/E11882_01/server.112/e16544/toc.htm
HTH
Srini

Reference to other schema

Hello,
I want to model the following situation in SQLD DM:
- 2 schema's
- in 1 schema I define a view
- in the other schema I want to refer to this view in a view
Questions:
- Do I create each schema as a design or as a relational model in one design?
- How can I refer to the view of the other schema in the Query Builder?
SQLD DM version 3.3.0.734
Thanks in advance,
Joop

Hi Joop,
Do I create each schema as a design or as a relational model in one design?As a relational model in one design.
How can I refer to the view of the other schema in the Query BuilderYou an define a schema for view you are creating. If objects used in view definition belong to another schema they are include with schema name in generated select statement. By default objects in the same schema (as the view) are not prefixed with schema name - if you want schema name to be included then check "Include schema name in Query" check box on view dialog.
Philip

Restricting SYS user to View other schema's Tables

Hi All,
Oracle DB Version - 10R2
O/S - UNIX
Could anyone share docs or steps to prevent SYS user to view other schema's tables;
Thanks,
Deepak

Dear Deepak_DBA,
If you revoke every privilege and role from the SYS user i presume the SYS will continue to select any table from the relevant schema. SYS is a special user and not like the others.
For instance if you want to revoke the SYSDBA and the SYSOPER from the SYS user;
SQL> revoke sysdba, sysoper from sys;
revoke sysdba, sysoper from sys
ERROR at line 1:
ORA-01998: REVOKE failed: user SYS always has SYSOPER and SYSDBAI have never seen such documentation that describes how to revoke everything or at least the SELECT ANY TABLE privilege from the SYS user.
Please see more about the SYS and the SYSTEM users;
SYS and SYSTEM Users;
http://download.oracle.com/docs/cd/E11882_01/server.112/e10897/users_secure.htm#ADMQS12003
Regards.
Ogan

View Access Problem

HI All,
I have a requirement as explained below
I have a couple of tables availabe in XXDYN schema and i have to grant select and insert access on these tables to different users p16 and p17.
I also have to restrict the users p16 and p17 in the way such that p16 user can enter only p16 data and p17 user can only enter p17 data.
So to acheive the above requirement i followed the below approach.
I created the custom tables in XXDYN schema and granted select and insert permission to p16 and p17 users on these tables.
As i have to restrict the user p16 and p17 from entering erroneous data (i.e p16 user entering p17 user data and p17 user entering p16 user data)
I have created custom views on XXDYN tables with a where condition
for ex:
create or replace view p16.custom_table as
select * from xxdyn.custom_table
where column1_value='P16';
so the above view is created in p16 user schema, so that the p16 can enter only p16 users data and not p17 users data.
The problem is that now both the table and the view are visible to P16 user i.e P16.custom_table and xxdyn.custom_Table.
is there any way to hide the xxdyn.custom_Table from p16 user? so that only p16.custom_table is availabe to p16 user.
Thanks for your inputs.
Regards,
Nagesh Manda.

Hi Nagesh Manda,
Another approach would be deploy both views in the data schema, i.e.,
XXDYN.p15_custom_table
XXDYN.p16_custom_table
And then grant privileges on only the views to p15 and p16
Tom Kyte discusses this in the latest Oracle magazine
http://www.oracle.com/technology/oramag/oracle/08-nov/o68asktom.html
Your scenario looks exactly as the case for "further restrict access to data"
Regards
Peter

Can't see DDL of views from other schemas in Developer?

Hi,
I've seen elements of this problem in other threads but this problem of course has it's own twist.
I can see other schema's objects EXCEPT VIEW DDL.
I have given a user every role and priv that I can and they still can't see the view ddl of another schema. They can see procedures, functions etc. just not the view. I've found that if I use the user that created the users I can see the DDL of all subordinate users. Users created under that schema can not see each others views no matter what rights are given. Interestingly enough sometimes when I look to display view DDL it will flash the DDL briefly before blanking the screen. very frustrating. All the Toad fanboys are crowing about how they couldn't possibly use a tool that doesn't allow them to see other view source.
I have also looked for settings in the preferences but could find none.
Is this a bug? It seems like one to me.
Any help is greatly appreciated.
Thanks
Mark

We have a bug logged for this.
Sue

Error using views from other schema

Hello,
i recently had problems using the execute immediate statement in Object Types.
The SQL statement tried to select from some views which were owned by an other schema.
Although we had public synonyms on these views and the same dynamic sql could be used out of a stored procedure the usage in the object type raised a "table or view does not exist exception".
using the same views in the same schema where the object types belonged to, was ok.
example:
schema: scott
view: my_view
schema: dave
sql: "select from scott.my.view ....."
works well from a stored procedure, but nor if used in an object type
create the view in schema "dave" an then
sql: "select from my.view ....."
works fine.
So is someone aware of this behaviour?
Is this a bug or a feature?
regards
peter

Hello Geoff,
here is the sample code.
If the table my_table belongs to the same
schema runningthe code the code runs with
no exception.
But if the table belongs to an other schema
(lets say SCOTT),
only having global synonyms and the rigths to
select on it, the code will raise an exception "table or view does not exist"
even if we use SCOTT.my_table in the
select.
create type query_o as object(
dummy integer,
static function get_query return
varchar2;
create or replace type body query_o as
static function get_query return varchar2
as
query varchar2(4000) :=
'select ' | |
' f.amount_month ' | |
'into :r1 ' | |
'from ' | |
' my_table f ' | |
'where id=:p1 ';
begin
return query;
end;
end;
create type consumer_o as object(
amount_month number,
member function find(p_id in integer)
return consumer_o
create type body consumer_o as
member function find(p_id in integer)
return consumer_o
as
l_amount number;
begin
execute immediate query_o.get_query()
using out l_amount,
in p_id;
return consumer_o( l_amount );
end;
end;
kind regards
peetr

Restricted view access to other schemas 'showstopper' problem

Similar Messages

Maybe you are looking for