Re: Database link

A copy of this was sent to "Michiel Ploeger" <nospam.Michiel.Ploeger_at_Bluewater-Group.Com> (if that email address didn't require changing) On Tue, 21 Sep 1999 15:30:32 +0200, you wrote:

>Remember that database links are insecure!
>

but we've given them counseling and they feel much better about themselves now :)

There is more then one way to create a database link. This one (below) is a proxy link -- all users would show as a common user on the other database you are linked to. This is typically used to provide a read only view of data to people -- sort of like 'anonymous' access. You would create the user "username" on the remote site and grant them only "create session" and the privelege to SELECT from various objects.

You may not consider this 'secure' since the password is stored in sys.link$ (a table to which only a few should have access to)....

If you on the other handl:

create database link NAME using test.world;

then, everyone connects as themselves to the remote system and no passwords appear in link$.

Database links are not less secure then anything else.

>M. Ploeger
>
>Mario Bucsics wrote in message
><3fc5848e.1a55a1f2_at_usw-ex0102-010.remarq.com>...
>>
>>You could do this in the following way:
>>
>>create database link "linkname" connect to "username"
>>identified by "passwort" using "test.world";
>>
>>THis example is a privat database link, if you like to make
>>the link public include the public keyword after
>>the "create" .
>
>

--
See http://govt.us.oracle.com/~tkyte/ for my columns 'Digging-in to Oracle8i'... Current article is "Part I of V, Autonomous Transactions" updated June 21'st  

Thomas Kyte                   tkyte_at_us.oracle.com
Oracle Service Industries     Reston, VA   USA

Opinions are mine and do not necessarily reflect those of Oracle Corporation Received on Tue Sep 21 1999 - 09:10:23 CDT