From: Sybrand Bakker on
On Wed, 14 Jul 2010 23:24:17 -0700 (PDT), Krzysztof Cierpisz
<ciapecki(a)gmail.com> wrote:

>definitely I have only one Oracle home.
>there is only one tnsnames.ora file on my system.
>it's fairly new entry into tnsnames.ora file, and as mentioned above
>when I change tnsname entry from OXO into TEST both connections
>(sqlplus and dblink) work fine.
>
>thanks,
>chris

Which tnsnames.ora are you referring to? The one on the server?
Because it is that one which will be used by the database link!
You need to establish whether the source database server can connect
to the target database, your client is irrelevant.

------
Sybrand Bakker
Senior Oracle DBA

From: Krzysztof Cierpisz on
On 15 Jul., 18:29, Sybrand Bakker <sybra...(a)gmail.com> wrote:
> On Wed, 14 Jul 2010 23:24:17 -0700 (PDT), Krzysztof Cierpisz
>
> <ciape...(a)gmail.com> wrote:
> >definitely I have only one Oracle home.
> >there is only one tnsnames.ora file on my system.
> >it's fairly new entry into tnsnames.ora file, and as mentioned above
> >when I change tnsname entry from OXO into TEST both connections
> >(sqlplus and dblink) work fine.
>
> >thanks,
> >chris
>
> Which tnsnames.ora are you referring to? The one  on the server?
> Because it is that one which will be used by the database link!
> You need to establish whether the source database server can connect
> to the target database, your client is irrelevant.
>
> ------
> Sybrand Bakker
> Senior Oracle DBA

I was referring to tnsnames.ora file on my local server (EMEADB11)
it is actually the same entry used from my client when executing
sqlplus (in this case client and server are same machines)
tnsname entry points to remote server.

--
chris
From: Krzysztof Cierpisz on
On 15 Jul., 15:14, Mark D Powell <Mark.Powe...(a)hp.com> wrote:
> On Jul 14, 2:21 pm, Mladen Gogala <n...(a)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
From: Carlos on
On Jul 16, 9:52 am, Krzysztof Cierpisz <ciape...(a)gmail.com> wrote:
> On 15 Jul., 15:14, Mark D Powell <Mark.Powe...(a)hp.com> wrote:
>
>
>
> > On Jul 14, 2:21 pm, Mladen Gogala <n...(a)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.
From: gazzag on
On 16 July, 10:56, Carlos <miotromailcar...(a)netscape.net> wrote:
>
> Ask the DBA, but this will probably be the answer.
>
> It seems it was a global dbname / GLOBAL_NAMES issue after all... ;-)
>
> Cheers.
>
> Carlos

He shoot, he scores! First the World Cup, now this... You're on a
roll :D

-g