Hi Guys,

I need some help in creating DB Links.

1. While I read the documentation for DB link creation, I found that
TNSNAMES.ora entry of the target DB is essential to create the DB link
( in USING clause of the DB link syntax

Incidentally, my organization uses LDAP to resolve/identify the
database. In this situation, how can i create the DB linkin

2. I need to create DB link object on schema A to connect to schema B.
Both schema A and B are on the same instance.

Something like

create database link link_from_a_2_b
connect to b identified by bpass
using <i dont know what should be given here as said in #1 >

The question I have is : Can a DB link of this sort be created?

I understand that referencing objects in B from A this way is not a
ideal method since we can grant permissions to A to access objects in
B. However, there is a possiblity that B might be moved to a new
instance in future. So if I create a DB link, movement of B across
different instance would be much quicker.

Thanks in advance for your assistance in this regard.

Cheers
Arun

On Mon, 08 Aug 2011 22:56:39 -0700, Arun wrote:

If ever RTFM was an appropriate answer, it's in this case. Do you have a
DBA in your organization? Please, ask him to tell you about the facts of
life, birds, bees, LDAP and DB links.



--
http://mgogala.byethost5.com

Mladen:

# If ever RTFM was an appropriate answer, it's in this case.

Yup ... you got it.

How many people have documented setting up and testing database links
in the history of the internet? How hard can it be to find documented
examples if you are not interested in reading the manuals?


# Do you have a DBA in your organization? Please, ask him to tell you
about the facts of
....

Plus a crazy little thing called love!

On Wed, 10 Aug 2011 05:02:06 -0700, John Hurley wrote:

What are you trying to say? That I was wrong for telling him to read the
manuals? The question he's asking is so simple that it can easily be
answered by documentations. If you want idiot-friendly list, go to
oracle-l.



--
http://mgogala.byethost5.com

Mladen:

# What are you trying to say? That I was wrong for telling him to read
the manuals?

Ummm ... no ... if you look at my response the first thing I said was
something like "Yup you got it.

I find it simply amazing that people cannot locate information like
this on their own ( either from the manuals or from wherever ).

Especially something as straightforward as a link that has probably
been blogged about a million times.

On 10.08.2011 17:53, Mladen Gogala wrote:
I guess John means it's even simpler to google explanations if someone
is not willing to read the whole manual - which of course would be the
default approach.

Cheers

robert

--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

On Aug 9, 1:56*am, Arun <set... (AT) gmail (DOT) com> wrote:
Database links are for accessing remote Oracle instances. Why not
define a synonym for each user B object that user A uses then when
user B is reloaced to a new instance just update the synonym to refer
to the remote version of the table? Create [public] synonym tableA
for userB.tableA@remote_db

HTH -- Mark D Powell --

On Aug 10, 8:58*am, John Hurley <hurleyjo... (AT) yahoo (DOT) com> wrote:
I gotta admit, I had problems this morning setting up a dblink to
newly installed 11g XE beta using the same scripts that had worked
perfectly a few months or years ago to two different 10g XE, or so I
thought. All documented, but the errors can misdirect. I think the
dash character should be allowed at least as a quotable character in a
dblink definition, since it is completely reasonable for a host to
have that in a name. Having to put in a domain name (even a bogus
one) to avoid getting the local domain is just strange. The host is
in the tnsnames, why should I have to?

And there are some way off blogs out there.

jg
--
@home.com is bogus.
http://www.signonsandiego.com/news/2...lose-winnings/