DB link for one to many user access [message #475403] |
Tue, 14 September 2010 17:25  |
caprikar
Messages: 226 Registered: March 2007
|
Senior Member |
|
|
Hi,
I need to create one to many user DB link in oracle 10g. Meaning I have a user A in database 1 and I want to access the objects from user B,C,D in database 2, how to create a public database link so that i can have this one to many user access?
Thanks
|
|
|
|
|
|
|
|
|
Re: DB link for one to many user access [message #475793 is a reply to message #475676] |
Fri, 17 September 2010 11:29   |
jesuisantony
Messages: 166 Registered: July 2006 Location: Chennai
|
Senior Member |
|
|
Hi Caprikar,
You have created private database link using SYS. Hence it is not accessible for a non-sys user. Try to create a PUBLIC database link and check. As Michel has mentioned, you cannot have a DB name in the place of a schema name.
Regards,
Antony
|
|
|
Re: DB link for one to many user access [message #475794 is a reply to message #475793] |
Fri, 17 September 2010 11:32  |
 |
Michel Cadot
Messages: 68737 Registered: March 2007 Location: Saint-Maur, France, https...
|
Senior Member Account Moderator |
|
|
Quote: As Michel has mentioned, you cannot have a DB name in the place of a schema name.
You can have a schema with the same name as the database name but using the database name at the place of schema name is not correct.
Regards
Michel
|
|
|