Re: Remote Database Link

The names.default_domain controls whether you need a 'fully qualified' alias name in your connect string:

For Instance, given mydb.world as a tnsnames.ora entry: If names.default_domain is not set or is set to anything other than 'world' then to connect you would need connect me/mypassword_at_mydb.world

If, however, names.default_domain IS set to 'world' then the connect command would be connect me/mypassword_at_mydb

( on the issue of global_names = true, if the remote database has this set to true, then the dba link name MUST match the global database name of the remote database...If it is set, the error message you get will provide you with the name you need to use:
Something like dba link rlink connect to database oraremote.world If you get this, create a link called oraremote.world-  global_names = false , then the dba link can be any name you like..but remember, it is the REMOTE database's init<sid>.ora setting that is controlling..)

hth

"Mr. Lynn Moorhead" <lynncind_at_swbell.net> wrote:

>Thanks Paul,
>
>The SQLNET.ora Authentication_Services setting may be the issue. I won't
>have an opportunity to check before this evening, but it will be the FIRST
>thing that I look at. Yes, I am authenticating a a member of ORA_DBA, AND I
>had been connecting as sysdba. However, I had tried it as both a normal
>user and sysdba.
>
>I also just realized that their is also a DEFAULT_DOMAIN setting in the
>SQLNET.ora file that MAY not be set correctly either. It should be, but I
>don't recall if the machine was originally configured while in the same
>Domain. I don't know what effect if any that this might have?
>
>Thanks again for the input, and I'll give this a "shot" this evening.
>
>Lynn :-)
>
>"Paul Drake" <paled_at_home.com> wrote in message
>news:3B3AB37E.3D788F4C_at_home.com...
>> "Mr. Lynn Moorhead" wrote:
>> >
>> > I get a message like "linkname attaches to linkname", which is obviously
>> > where I want it attached. However, it doesn't actually appear to be
>> > functioning. I have successfully created a "Remote Database Link" from
 the
>> > Windows 2000 machine to the Windows NT 4.0 machine (actually from two
>> > different Win2k machines to the NT 4.0 machine), but I cannot seem to
 create
>> > it in the opposite direction. It has been suggested to me by a friend
 that
>> > it could be a privileges issue or some sort of Authentication difference
>> > between 2000 and NT 4.0. I've "dotted all the I's and crossed all the
 T's"
>> > so to speak, but I must have missed some ADDITIONAL requirement when
 trying
>> > to go from an older OS to a newer one. It seemed like such a simple
>> > question, but I haven't found anyone who has done it or had a need to do
 it
>> > in this manner.
>> >
>> > I'm trying to get approval to upgrade this "questionable" machine to
 Win2K
>> > which will make this all irrelevant, but I'm still interested in the
 answer
>> > in case I encounter this again in the future. ANY HELP would be greatly
>> > appreciated.
>> >
>> > Lynn :-)
>> >
>>
>> init.ora:
>> global_names = true
>>
>> sqlnet.ora:
>> SQLNET.AUTHENTICATION_SERVICES= (NTS) -- are you authenticating as a
>> member of ORA_DBA group?
>> NAMES.DIRECTORY_PATH= (TNSNAMES, HOSTNAME, ONAMES) -- might you have
>> other naming methods in use?
>>
>> just 3 ideas of places that could go wrong.
>> connect to each database as a user, not using "/ as sysdba".
>>
>> hth,
>>
>> Paul
>>
>

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- http://www.newsfeeds.com - The #1 Newsgroup Service in the World! -----== Over 80,000 Newsgroups - 16 Different Servers! =----- Received on Thu Jun 28 2001 - 09:04:52 CDT