RE: Advice for dblinks between two prod DBs.

This is great advice.  Create a read-only user in the remote database.
Only grant access to the items it needs to see.  And again, I would
create views in the remote database that are granted to this user that
give only what is needed.  And pre-joining tables in this view aids
querying immensely - the joins happen on the remote database.  This
speeds things up tremendously!

 


--------------------------------------------------------
This transmission may contain confidential, proprietary, or privileged 
information which is intended solely for use by the individual or entity to 
whom it is addressed.  If you are not the intended recipient, you are hereby 
notified that any disclosure, dissemination, copying or distribution of this 
transmission or its attachments is strictly prohibited.  In addition, 
unauthorized access to this transmission may violate federal or State law, 
including the Electronic Communications Privacy Act of 1985.  If you have 
received this transmission in error, please notify the sender immediately by 
return e-mail and delete the transmission and its attachments.


________________________________


From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Dennis Williams
Sent: Wednesday, November 22, 2006 1:44 PM
To: Rich.Jesse@xxxxxx
Cc: Hemant K Chitale; oracle-l@xxxxxxxxxxxxx
Subject: Re: Advice for dblinks between two prod DBs.

 

Jesse,

 

From reading your posting and the replies, I don't see one aspect
mentioned.

One of the drawbacks of a database link is that it gives access to the
entire schema, particularly troubling where ERP systems are involved. A
practice I've used is to create a special username on each end of the
database link. On one end, that username owns the database link. At the
other end, that username is granted select only privilege to the needed
tables. Synonyms can simplify a complicated syntax. 

 

Just a tip.

Dennis Williams

Other related posts: