Privileges to view another schema

Hi there,
I am sorry if this topic has been covered in another thread, but cannot seem to find it. I have a workspace called DAVE with some objects in it. I also have another schema MERCURY that I would like to use in the DAVE APEX workspace. I have done a GRANT ALL on the MERCURY objects to DAVE but cannot see them in my workspace.
Obviously I am missing something - Can someone please tell me what it is ??????

Hi,
Are you looking objects using workspace Object browser ?
If you like use object browser, then you need add another schema to your workspace
http://download.oracle.com/docs/cd/E17556_01/doc/admin.40/e15521/adm_mg_wrkspc.htm#CHDFAECE
Regards,
Jari

Similar Messages

VIew of Package body in another schema in EA 3.0

I would like the ability in SQL Developer to view the package body of another schema with the CREATE ANY PRIVILGE.
For instance, in TOAD you can grant access to DBA_SOURCE or SELECT_CATALOG_ROLE and then be able to view another schema's package body.
This is long overdue without having to log into that schema or granting CREATE ANY PRIVILEDGE to user.
This one is really needed

"CREATE ANY PRIVILEGE" is irrelevant to the ability of viewing the source owned by other users.
Please provide exact script for creating a user, which is able to see the code, say in HR schema, via the query
select * from all_source
where owner = 'HR'
and yet missing the nodes in the OtherUsers->Packages->PKG_A->PKG_A Body in the navigator.

How do I view package bodies in another schema ?

For purposes of SOX and security/audit control, we log in under our network id's in our production environment. We have sourcecode compiled into Oracle seeded schemas ( APPS ) so that scheduled jobs are able to run with submitted from the Oracle Applications environment. We don't compile code into our personal network account areas.
I know how to GRANT EXECUTE privs so that we can execute a package in another schema, but what I want to do is to be able to view the sourcecode in another schema. Compile into APPS but be able to see the package body from my network id schema account.
I can't seem to find what the correct permission is anywhere. Granted I can look at DBA_SOURCE to get to it, but I want to use a tool like SQL Developer or TOAD to look at the code in a more presentable and easier to debug manner.
Any help ?

I did some more searching on the forum... seems its already a request... TOAD gives access to DBA_Views to resolve the issue... SQL Developer has not integrated that functionality yet, but forum entries seem to indicate that it is on the horizon.
Thanks for responding though.
~Barry

Spatial query on join view in another schema

Background:
I have a schema with tables containing four spatial columns per table. I have a second schema that contains join views of the tables in the first schema. The join view consists of the attributes and any other tabular data that is joined via foreign key to non-spatial tables and one of the four geometry columns. I have a third schema that owns no database objects of its own, but has select privilege to the second schema's view objects.
We are using Oracle 10.2.0.2 on a windows platform.
This worked in 9i, the problem only presented itself when we migrated to 10g.
Problem:
When I run a spatial query on a join view in the second schema(the schema that owns the object), it runs and returns results in about a second. When I run the exact same query in the third schema it routinely takes 20-30 seconds.
Here is the query that I run in both schemas with varying query times:
SELECT COUNT(*)
FROM two.join_view_a A
WHERE (MDSYS.SDO_FILTER(A.GEOM, SDO_GEOMETRY(2003,8307,NULL,SDO_ELEM_INFO_ARRAY(1,1003,3),SDO_ORDINATE_ARRAY(26.6396,26.5708,43.346,34.4083)),'QUERYTYPE=WINDOW')='TRUE');
Question:
Why does this happen?
What can I do to fix this problem?
Thanks,
John

Have a read of this posting: Oracle spatial view runing slow as different user
There are details there about the 'optimizer_secure_view_merging' parameter and the effect it can have on cross schema views in 10.2

Spatial query on view to another schema

Hi,
I am getting the following error on this query :
select ufi from cadastre where
sdo_filter(geometry,
mdsys.sdo_geometry(2003,8311,NULL,
sdo_elem_info_array(1,1003,3),
sdo_ordinate_array(130.967,-12.510,131.000,-12.486))) = 'TRUE';
ORA-13226: interface not supported without a spatial index
Cadastre is a view of a table stored in another schema.
This query works :
select ufi from sdo_owner.parcel where
sdo_filter(geometry,
mdsys.sdo_geometry(2003,8311,NULL,
sdo_elem_info_array(1,1003,3),
sdo_ordinate_array(130.967,-12.510,131.000,-12.486))) = 'TRUE';
I have an entry in user_sdo_geom_metadata for CADASTRE , do i also need an entry in user_sdo_index_info for the query to work.
Does any one have any ideas ?
James

Dan,
I have worked out why it happens. We have a parcel table that is made up of polygons and points. The points are parcel's that have no legal boundary or survey boundary, just a point where a house might be located.
What i had forgotten was that i had created a function to convert these points into a polygon on the fly. This buffer function is called from the view.
example
create view cadastre
as
select
ufi,
parcel_key,
buffer(geometry) "GEOMETRY"
from sdo_owner.parcel;
I am guessing that because the geometry is no longer geometry from a table but created geometry it does not have a spatial index associated with it.
Here is the buffer function
CREATE OR REPLACE FUNCTION buffer
geometry MDSYS.SDO_GEOMETRY,
layer_name VARCHAR2
RETURN MDSYS.SDO_GEOMETRY
AS
temp_geom MDSYS.SDO_GEOMETRY;
diminfo MDSYS.SDO_DIM_ARRAY;
start_x FLOAT;
start_y FLOAT;
end_x FLOAT;
end_y FLOAT;
BEGIN
SELECT u.diminfo INTO diminfo
FROM user_sdo_geom_metadata u
WHERE u.table_name = UPPER(layer_name);
IF geometry.GET_GTYPE() = 1 THEN
temp_geom := sdo_geom.sdo_buffer(geometry,diminfo,4,'units=m arc_tolerance=0.005');
return temp_geom;
END IF;
IF geometry.GET_GTYPE() = 2 THEN
temp_geom := sdo_geom.sdo_buffer(geometry,diminfo,4,'units=m arc_tolerance=0.005');
RETURN temp_geom;
END IF;
IF geometry.GET_GTYPE() = 6 THEN
temp_geom := sdo_geom.sdo_buffer(geometry,diminfo,4,'units=m arc_tolerance=0.005');
RETURN temp_geom;
END IF;
RETURN geometry;
END;
James

View package body in another schema

I have developers who want to view the code in the package body in another's schema.
I know select text from all_source/ user_source works only for packages in your own schema.
Granting system privelege 'create any procedure' allows the developer to view as well as update priveleges.
As the owner of the objects what grants do I need to give to developers so that they can only view the code.

You can grant select_catalog_role permissions to your developers. This will give your developers select access to all of the V$ views and DBA_% views. Then they can view the dba_source table to view other schema's package code..
Regards,
David

Cant view objects from another schemas

Hi everybody!
I have a 10.1.2 Jdeveloper and a 9.2.4 Oracle database.
I successfully created a database connection.
With provided login I can access to tables from another schemas in SQL Worksheet, but I cant see any objects from those schemas in the connection tree.
What's wrong?

The Schemas are being filtered so that you only automatically see the schema for the connection that you logged on with. To change the schemas that are visible you need to :
1) Select the connection name in the Navigator (you should see that it has a filter icon overlaid showing that it is being filtered)
2) Invoke the context menu and select 'Apply filters'
3) Shuttle over the other Schemas you wish to see and press OK
Regards,
Lisa Sherriff
JDev QA

How can i access all the objects of one schema from another schema

Dear All,
How can i access all the objects(Tables,Views,Triggers,Procedures,Functions,Packages etc..) and do the modifications of one schema from another schema (Without using synonyms concept).
Thanks in advance,
Mahi

First of all, synonyms only help you easy reference the object. It doesn't have any implication of object privilege.
As long as you have proper privilege on target object. You can access it with or without synonyms.
Assuming you have proper privilege of objects, you can use following command to assume schema owner.
ALTER SESSION SET CURRENT_SCHEMA = Schema_owner

How to share data in "User_*" tables with another schema

I would like to share the data in the USER_SEGMENTS table with another schema. If I create a view and grant select on the view, when the other schema queries the view the data is identical to themselves querying the SYS.user_segments table directly.
create view sys_user_segments as select * from sys.user_segments;
grant select on sys_user_segments to A;My guess is that the SYS.user_segments table is a view based on the current user.
Is there a way to share this data without creating a copy of the table?
Oracle: 10g
Thanks

Hi,
All the data dictionary "tables" whose names start with user_ (or all_ or dba_) are actually views, and what results they bring back depend on what schema you logged in to. I don't think there's any way to allow user A to directly see what's in user B's version of user_segments.
Why do you need this? Can you use the all_ views instead, by giving A some privileges on B's objects?
Failing that, you can replicate the data into a regular table. Inside a AUTHID DEFINER stored procedure, the data dictionary views (such as user_segments) are the versions of the procedure owner, so B can write a stored procedure (let's call it populate_my_segments) that populates a regular table (let's call it my_segements), and then grant EXECUTE privilges on populat_my_segments and SELECT privileges on my_segements to user A. A can then refresh the table and look at it whenever he wants to.
If A only needs to see a little information, e.g. the total number of bytes, from B's user_segments, then B can write a function just to return that information.

Granting Read Only Access to user in another schema

Oracle Database 10g
Red Hat Enterprise Linux Server release 5.3
We are requested by a developer to grant his account read only access to TABLES, VIEWS, INDEXES, SEQUENCES, FUNCTIONS, PROCEDURES, PACKAGES, TRIGGERS, JOBS of another schema.
I know granting read only access to Tables and Views. But is it possible to grant READ ONLY access to other mentioned objects ? How to do it ?
And some views are in INVALID status.
I tried to compile them using alter view owner.viewname compile;
But got this ---- Warning: View altered with compilation errors.
Those views are still in INVALID status. And then I tried to use utlrp.sql . Same result.
Then I used the following
SELECT TEXT FROM DBA_VIEWS WHERE VIEW_NAME='view-name';
select REFERENCED_NAME,REFERENCED_TYPE from dba_dependencies where name='view-name';
It turns out some reference types are non existent.
Does that mean DBAs cannot do anything about this ?

Nilton wrote:
We are requested by a developer to grant his account read only access to TABLES, VIEWS, INDEXES, SEQUENCES, FUNCTIONS, PROCEDURES, PACKAGES, TRIGGERS, JOBS of another schema.
I know granting read only access to Tables and Views. But is it possible to grant READ ONLY access to other mentioned objects ? How to do it ?
TABLES -> YES grant SELECT
VIEWS -> YES grant SELECT
SEQUENCE -> YES grant SELECT
INDEXES -> There is no read access for indexes...indexes are put on tables and a user who has read access on tables can read the index as well.
FUNCTIONS / PROCEDURES / PACKAGES -> I am not sure what you mean by read access on procedures, functions and packages. You may grant EXECUTE privilege on these.
TRIGGERS -> there is no read access on triggers required. They are implemented on tables for a DML event. If the user has DML access he has the execute access on the trigger as well.
JOBS -> I am not sure what to read from Jobs.
And some views are in INVALID status.
I tried to compile them using alter view owner.viewname compile;
But got this ---- Warning: View altered with compilation errors.
Those views are still in INVALID status. And then I tried to use utlrp.sql . Same result.
Then I used the following
SELECT TEXT FROM DBA_VIEWS WHERE VIEW_NAME='view-name';
select REFERENCED_NAME,REFERENCED_TYPE from dba_dependencies where name='view-name';
It turns out some reference types are non existent.
Does that mean DBAs cannot do anything about this ?There are compilation errors in the Views. e.g. the view may be referring to a table which doesn't exist etc.
Unless you fix the error in the view you can't compile it and male it valid. Fix the view errors. If objects are non existing create them or refer to view to some where else.
If the nonexistent objects were mistakenly dropped, or the data file which contained those objects was dropped, no matter what was the reason for that object to be gone a DBA can bring it back if he is a well prepared DBA and has setup his database for such kind of disasters.
Now tell us why those objects are non-existent ? were they meant to be gone ? or they were dropped mistakenly?
Now here are my guesses:
If they were meant to be gone then probably the views definitions need to be adjusted not to refer them anymore.
If they were mistakenly dropped then:
Do you have them in recyclebin? (only tables) if YES just FLASHBACK TABLE <<tablename>> AS BEFORE DROP.
Is your database has Flashback database ON? if YES FLASHBACK DATABASE until 'time/scn just before the object was dropped'
Do you have backups and your database is running in ARCHIVE LOG mode? if YES perform an incomplete recovery using RMAN.

Calling PL/SQL Procedure In Another Schema Gives Unexpected Result

I have a SQL Script that does this:
conn pnr/<password for user pnr>;
set serveroutput on;
exec vms.disable_all_fk_constraints;
SELECT owner, constraint_name, status FROM user_constraints WHERE constraint_type = 'R';
and the disable_all_fk_constraints procedure that is owned by user 'vms' is defined as:
create or replace
procedure disable_all_fk_constraints is
v_sql VARCHAR2(4000);
begin
dbms_output.put_line('Disabling all referential integrity constraints.');
for rec in (SELECT table_name, constraint_name FROM user_constraints WHERE constraint_type='R') loop
dbms_output.put_line('Disabling constraint ' || rec.constraint_name || ' from ' || rec.table_name || '.');
v_sql := 'ALTER TABLE ' || rec.table_name || ' DISABLE CONSTRAINT ' || rec.constraint_name;
execute immediate(v_sql);
end loop;
end;
When I run the SQL script, the call to vms.disable_all_fk_constraints disables the FK constrains in the 'vms' schema, whereas I wanted it to disable the FK constraints in the 'pnr' schema (the invoker of the procedure). I know that I could make this work by copying the disable_all_fk_constraints procedure to the 'pnr' schema and calling it as "+exec disable_all_fk_constraints;+" from within the SQL script but I want to avoid having to duplicate the PL/SQL procedure in each schema that uses it.
What can I do?
Thank you

You have two issues to solve.
First you need to write a packaged procedure that works with INVOKER rights. The default is DEFINER rights.
The difference is excatly what you need. Usually the package has the rights from the schema where it is defined (=Definer rights). In your case schema VMS. Whereas you need the privileges from the user that calls the package (PNR).
=> Check out the documentation for INVOKER rights
The second problem is that the view "user_constraints" will not give the results you expect when called from inside a procedure in another schema. An alternative could be to use the view DBA_CONSTRAINTS with a filter on the owner (where owner = 'PNR'). Not sure if there are other working possibilities. Well you could create a list of constraint names that you want to disable, instead of creating the list dynamically.
And you could have another potential disaster creeping up upon you. If you run this thing, then at this moment you don't have any referential integrity anymore. You can't be sure that you can create the FKs again after this action. This is EXTREMLY DANGEROUS. I would never ever do this in any kind of production or test database. I would be very careful when I do it on a development database.

To kill session in one schema from another schema

Hi Team,
I got a problem like a table from one of my schema has been locked. I am getting 'ORA-00054: resource busy and acquire with NOWAIT specified' error when trying to delete rows from that table or even when trying to truncate that table.
Let the table be 'T1' present in schema 'VIEW'
I tried to kill the session which is active for that schema by below query
select sid,serial#,status from v$session where username='VIEW' and STATUS = 'ACTIVE';
alter system kill session '681,2586';
But i couldn't do the above as i don't have DBA privilege for that. But i have DBA privilege for another schema let it be 'ADMIN'
Now how can i kill the session in schema 'VIEW' from schema 'ADMIN'
can any one get me solution.
Thanks in Advance
11081985

I got a problem like a table from one of my schema has been locked. I am getting 'ORA-00054: resource busy and acquire with NOWAIT specified' error when trying to delete rows from that table or even when trying to truncate that table.
Before you do anything why don't you actually find out WHY that table has been locked.
You generally should NOT be killing sessions without knowing what is causing the problem to begin with.
Then you also need to determine if you should use KILL SESSION or instead use DISCONNECT SESSION and well as whether the use of IMMEDIATE is appropriate.
Each of those choices acts differently. Many people use KILL when they should really use DISCONNECT.
See DISCONNECT SESSION Clause and KILL SESSION Clause in the ALTER SESSION chapter of the SQL Language doc
http://docs.oracle.com/cd/E11882_01/server.112/e17118/statements_2014.htm#i2282145

Create user who can update another schema table

Hi,
We have a prod system under which we need to update the application schema by running different update statement and create/execute function,procedure,package body. This is very easy if you use the owner schema. But i need to run those activities from another user due to some restriction. How can i do that??
May u suggested to give update any table privilege..but this would give all the dictionary table access also.
Is there any privilege that would allow any other user to update another schema table without using the schema name infront of the table name??
Plss suggest

John,
Can we use public synonym for it ? I don't know the security risk for it though :
SQL> connect hr/hr
Connected.
SQL> select * from scott.emp;
select * from scott.emp
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> connect scott/tiger
Connected.
SQL> create public synonym scotemp for scott.emp;
Synonym created.
SQL> connect hr/hr;
Connected.
SQL> select * from scotemp;
select * from scotemp
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> connect scott/tiger
Connected.
SQL> grant select on emp to hr;
Grant succeeded.
SQL> connect hr/hr
Connected.
SQL> select * from scotemp;
14 rows selected.
SQL> show user;
USER is "hr"
SQL> update scotemp set ename='SMITHX' where empno=7369;
update scotemp set ename='SMITHX' where empno=7369
ERROR at line 1:
ORA-01031: insufficient privileges
SQL> connect scott/tiger
Connected.
SQL> grant update on emp to hr;
Grant succeeded.
SQL> connect hr/hr
Connected.
SQL> update scotemp set ename='SMITHX' where empno=7369;
1 row updated.
SQL> rollback;
Rollback complete.
SQL>
Regards
Girish Sharma

SQL Plan Management - Baseline- Can it be used in another Schema

Hi,
I have never implemented, SQL Plan Management -Creating SQL plan baselines.
I am having a query which is using indexes in one Schema.
On another Schema in the same DB, the query accesses the SAME TABLE THROUGH SYNONYM. And the plan is very different. And query goes into indefinite execution.
I have tried hints and other ways but it's simply not using the indexes.
Anyone having experience with Baselines, can you suggest if I create a Baseline for the plan in SchemaA.
Then can I use the same plan through Baseline in SchemaB for the same query?
Please suggest..Thanks..

Hi Jeneesh,
Thanks for the reply.
Problem is that the query has Xquery code inside and it's using the XMLType indexes. That's why it does not seem to be using the XML Indexes even by Hints.
I have posted the scenario in XMLDB Forum as well:
Re: Table in Schema1 using XMLIndexes But not in View- Schema2
But can you think of any harm if I try to create Baseline and tag the query with it.
So even in other schema if the same query is fired it will use the right Explain Plan.
I am not able to figure out any other way right now.
Please suggest..Thanks..

VPD: Problems calling a function on another schema

Here's the setup:
I've create a schema called "AllYourBase". It contains all of my tables, views, functions, procs, etc.
These tables are protected by a DBMS_RLS policy. The policy uses a function to define its predicate which looks like this:
create or replace function tous_filter(schemaName varchar2, tableName varchar2)
return varchar2 is
begin
return 'account = sys_context(''USERENV'', ''CLIENT_IDENTIFIER'')';
end;
All of the tables have an account column for this to work. So far, this is a pretty basic VPD setup.
I have other db users that login and view data in the "AllYourBase" schema.
So when "ArbyLong" logs in, I set sys_context('USERENV', 'CLIENT_IDENTIFIER') to "ArbyLong", and when he runs a query, he gets back his rows.
Now, "AllYourBase" has several functions. Here's a very contrived, simplified example of one (but it illustrates the issue I'm running into just fine):
create or replace function getUserID
return integer is retval integer;
begin
select user_id into retval from users;
return (retval);
end;
When "ArbyLong" runs the equivalent query (select user_id from users), he gets back the one row where the account column is equal to "ArbyLong", as expected.
But this getUserID function lives in the "AllYourBase" schema. And here's the catch: I've made "AllYourBase" exempt from the policies by running "grant exempt access policy to AllYourBase".
When "ArbyLong" runs the function getUserID, it runs in the "AllYourBase" schema and pulls ALL of the rows from the users table.
This particular function simply errors out (since it's only expecting one row), but other functions are returning data that the logged in user shouldn't see.
So even though there are policies in place, by calling a function on another schema who is exempt from the policies, a user is able to see all returned data and not just the rows they are normally limited to.
Ultimately my question is this: Is there a way to enforce VPD policies when a user calls a function that lives in another schema?
Doing my own research, the answers I've come up with are:
* Don't use "grant exempt policy"!
* Put the function directly into the users' schemas. So "ArbyLong" would have his own getUserID function that would look at the "AllYourBase" users table.
I'd rather not do either of these, so does anyone have any other ideas? If it turns out these are the only solutions, then I'll go with one of them.
Thanks!

Need more info. Are you using a ViewStack or other navigator container, and trying to access a view that has not been displayed yet, due to deferred instantiation?
If this post answers your question or helps, please mark it as such.
Greg Lafrance - Flex 2 and 3 ACE certified
www.ChikaraDev.com
Flex Training and Support Services

Privileges to view another schema

Similar Messages

Maybe you are looking for