SqlPlus connection error ORA-12545

[sambavan]

Could you provide me the OS and DB version of your server and the clients... Is your DB us SE/EE?

mts_dispatchers = "(protocol=TCP)(DISPATCHERS=2)" 
mts_servers = 5
mts_max_servers = 10 
mts_max_dispatchers = 10

Sam

[Edited by sambavan on 10-30-2001 at 03:55 PM]

[ann1]

Here is the result. I noticed the dispatcher host is NT3.MYCOMPANY.NET instead of just NT3. I think it is caused by the recent DNS configuration of the machine into the MYCOMPANY.NET domain, while before it was empty.

C:\>lsnrctl services

LSNRCTL for 32-bit Windows: Version 8.1.7.2.0 - Production on 30-OCT-2001 15:56:
44

(c) Copyright 1998 Oracle Corporation. All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=111.111.111.11)(PORT=1521)))
Services Summary...
PLSExtProc has 1 service handler(s)
DEDICATED SERVER established:0 refused:0
LOCAL SERVER
orcl has 1 service handler(s)
DEDICATED SERVER established:0 refused:0
LOCAL SERVER
orcl has 2 service handler(s)
DEDICATED SERVER established:1 refused:0
LOCAL SERVER
DISPATCHER established:5 refused:0 current:0 max:1022 state:ready
D000
(ADDRESS=(PROTOCOL=tcp)(HOST=nt3.MYCOMPANY.NET)(PORT=1664))
The command completed successfully

[sambavan]

What do you get when you do

 

select * from global_name;

This should be the service name in your tnsnames.ora file.

Could you check that please...

Sam

[sambavan]

also please post your sqlnet.ora file specs


Sam

[ann1]

OS is NT4.0 Sp6; DB is Oracle8.1.7.2.1.

The global name was orcl.world. But after changed to orcl.nt3, the result is the same. The global_name does not affect the connection (as by definition, it affects dblinks), since the tnsname is using service_name defined as orcl.nt3.

SQLNET.ORA

SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES)

It just seems that the dispatcher constructed the host name from the DNS setup. How can I force it to be nt3 instead of nt3.mycompany.net?

*********
DISPATCHER established:5 refused:0 current:0 max:1022 state:ready
D000
(ADDRESS=(PROTOCOL=tcp)(HOST=nt3.MYCOMPANY.NET)(PORT=1664))
************

[sambavan]

Now, could you comment out the

SQLNET.AUTHENTICATION_SERVICES= (NTS)

in your sqlnet.ora file and try the connection again.

On the other hand you can set the

local_listener = "(Address=(PROTOCOL=TCP)(HOST=...)(PORT=1521))"

in your initSID.ora file and restart the instance and then check that the dispatcher registers the correct server. Also make sure that things are configured as you want in the listener.ora file too...

Sam

[ann1]

Still no luck. I am going to contact Oracle support.

[sambavan]

Did you configure your host name to the dispatcher host name and try?

Sam

[ann1]

Yes. Same result.

[sambavan]

Ann,

I couldn't think of any thing more other than this

MTS_DISPATCHERS = "(ADDRESS= (PROTOCOL=TCP)(HOST=chmweckerl1) ) (DISPATCHERS=4)"

Stop and start the instance

check listener services and try your connection again...

Extract from metalink

You can fix the problem by adding the Oracle listener host name and IP to the
hosts file on the Microsoft client machine.

The file is located in the following directory:

C:\WINNT\system32\drivers\etc

The filename is "hosts"

Edit the file to include the IP address and the host name of the Oracle server
to which you wish to connect, thus:

126.34.10.244 hostname.domainname.com hostname othernames


Be careful not to add any extention to the file when saving it.

This is a workaround in the absence of a domain names server (DNS). The best
thing is to have DNS up and running and the client configured to use it.

Sam