restrict schema A from schema B
From: Joe Smith <joe_dba_at_hotmail.com>
Date: Mon, 11 Oct 2010 18:36:33 -0500
Message-ID: <BLU108-W263C175857D9FB75DDEB8197530_at_phx.gbl>
Date: Mon, 11 Oct 2010 18:36:33 -0500
Message-ID: <BLU108-W263C175857D9FB75DDEB8197530_at_phx.gbl>
How to restrict schema A from schema B.
I have a db with schema B. Our applications are written in C++ and they use schema B. We have to support a 3rd party product that will require us to install schema A ( that supports the 3rd party app ) in our db. How do I absolutely stop schema A from accessing schema B’s objects? Management want options on how to restrict access.
Besides from granting privileges and assigning roles how can I stop schema A from schema B’s objects? We already use security policies and have discussed building a separate db for schema A.
Has anybody else had this problem and how did they overcome it?
thanks.
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Oct 11 2010 - 18:36:33 CDT