RE: DB Links management

How does the global name help ?

If the DBLink is created without a identified by, the user must provide a password
each time it is used. Also, how can the DB Link be used in automated programs, views, Snapshots etc
How do you achieve seperation of schemas and privileges within the one database [whether local or remote database] ?

Hemant

At 10:18 AM Thursday, Hollis, Les wrote:
>Use global names and have only ONE link from DB1 to DB2, etc....
>
>
>Create public database link DB1 using 'DB1';
>
>
>Notice NO connect to/identified by
>
>This means you will have to have a global name for your database.....
>
>
>
>
>
>-----Original Message-----
>From: oracle-l-bounce_at_freelists.org
>[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Tony Vecchiet
>Sent: Wednesday, December 01, 2004 7:21 PM
>To: oracle-l_at_freelists.org
>Subject: DB Links management
>
>With all the SOX work and password rotations, how do most of you manage=20
>all the dblinks?
>No one wants to know anyone's passwords and we've already rebuilt the=20
>dblinks view to exclude
>the password column. Anyhow, the DBA group got assigned recreating all=20
>the dblinks
>because we can get into all the databases. Any one out there have a=20
>good method of managing
>this?
>thanks
>--
>http://www.freelists.org/webpage/oracle-l
>--
>http://www.freelists.org/webpage/oracle-l

Hemant K Chitale
http://web.singnet.com.sg/~hkchital

--
http://www.freelists.org/webpage/oracle-l