Re: dblink no listener - normal connection works

From: Carlos <miotromailcarlos_at_netscape.net>
Date: Fri, 16 Jul 2010 02:56:54 -0700 (PDT)
Message-ID: <aaf07f13-ede3-4abb-85c9-01a37a1ef07c_at_i28g2000yqa.googlegroups.com>

On Jul 16, 9:52 am, Krzysztof Cierpisz <ciape..._at_gmail.com> wrote:
> On 15 Jul., 15:14, Mark D Powell <Mark.Powe..._at_hp.com> wrote:
>
>
>
> > On Jul 14, 2:21 pm, Mladen Gogala <n..._at_email.here.invalid> wrote:
>
> > > On Wed, 14 Jul 2010 05:57:02 -0700, Mark D Powell wrote:
> > > > One of the default rules for a database link is that the link name must
> > > > match the remote database name: what is the name of the remote database?
>
> > > That is true only in the situations when the global_names=true, which is
> > > a recommended setting, though not the default one.
>
> > > --http://mgogala.byethost5.com
>
> > As an interesting side fact, I remember the default being true so I
> > checked the manuals:  Sure enough using 10.2 documentation it does
> > default to true but on 8.1.7 (which has 8.1.6 Reference) the default
> > was true. So I grabbed the 9.2 documentation and it was true there.
>
> > Krzysztof, what is the setting of global_names on the target
> > database?  I believe this parameter controls incoming requests and not
> > outgoing link names.
>
> > HTH -- Mark D Powell --
>
> I cannot see that value (no access to v$parameter)  -> it's a very
> limited account

Ask the DBA, but this will probably be the answer.

It seems it was a global dbname / GLOBAL_NAMES issue after all... ;-)

Cheers.

Carlos. Received on Fri Jul 16 2010 - 04:56:54 CDT