Re: Connecting to a remote db which has no domain name, but local db has global_names=true

DA Morgan wrote:
> Rob Cowell wrote:

--snip--
> > I probably didn't explain myself very well. db_domain is not set on the
> > remote server, and because that db is not controlled by my company we
> > can't get one set up easily. I was looking for a way to connect to that
> > database via a dblink while I have global_names=true on my db.
>
> And the default domain is?
> --

--snip--

I believe OP explained the situation quite clearly.

Assume, their database has db_domain "Y.Z" with global_name being "X.Y.Z"

The target database does not have db_domain set. Their global_name being "M".

Now if in source/their database one tries to create a database link to the target database (with global_names = true in source db): create database link M connect to user identified by pwd using 'M';

They are getting the error:
ORA-02085: database link M.Y.Z connects to M

This happens because the source/their database appends the source databases db_domain (from the global_name) to any database link which does not explicitly specify a domain. And if global_names =true, the database link name should match exactly to the target databases global_name.

This is a situation which really has only couple of solutions, none of which is ideal for OP:

• Change target database to define a db_domain .. and alter their global_name to have that db_domain
• Change their database to not have a db_domain in the global_names. A tall order because the replication setup would need to be rebuilt.
• Change global_names=false in their database. They cannot do this because MM replication requires this parameter to be set to true.

To OP,
Tough situation. I believe Oracle should have provided an easier option ..
but I don't think there is any other solution to this...

Anurag Received on Tue Jun 13 2006 - 12:30:08 CDT