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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Tony Vecchiet Sent: Wednesday, December 01, 2004 7:21 PM To: oracle-l@xxxxxxxxxxxxx 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 -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l