RE: password and dblink mgmt tool

That's basically what I said.....

A schema IS for all intents and purposes a userID. To own an object you have to create a user to do so...hence a userID.

SO, like I said grant the necessary object privs to the userid on the REMOTE DB as required...

-----Original Message-----
From: Hemant K Chitale [mailto:hkchital_at_singnet.com.sg]=20 Sent: Thursday, March 03, 2005 8:28 AM
To: Hollis, Les; oracle-l_at_freelists.org
Subject: RE: password and dblink mgmt tool

My database "users" are actually Application Schemas. End-users do not=20 have database accounts.
Database Links are requested by the Application Teams to "connect" two=20 databases running
different applications. Neither do I have the same username nor do I=20 expect the same username
present in the two databases. I setup a specific account with privileges=20
only on a subset
of tables/objects in the remote database to be used for the DBLink.

Hemant
At 09:57 AM Thursday, Hollis, Les wrote:
>You don't use a userid/password
>
>Create public database link PROD using 'PROD';
>
>
>
>If the user exists on source database and the destination database,
then
>statements will work. If user id does not match across DB's then they
>don't have any perms.
>
>Access to tables can be granted just like in the same DB. Grant
select,
>insert on tablename to username. Etc
>

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

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