Home » RDBMS Server » Networking and Gateways » listener running, but unable to listen client
listener running, but unable to listen client [message #222512] Mon, 05 March 2007 04:38 Go to next message
aboodlardy
Messages: 80
Registered: November 2006
Location: India
Member
Hi
I have install oracle 10gR2 on linux machine and oracle 9i on windows machine and connected both machines(verified using ping).
I created a database on linux machine using dbca, and i dont have any database on windows machine i just installed the software. I configure listener.ora on linux using default file just made the changes to sid and oracle_home.
I started the listener.
On window machine using netca i created netservice name(all information of linux machine given correctly) but when i test this connection using netca i am getting following error
ora:012560:tns protocol adapter error.
plz help
any suggestions.(sorry , posted twice but need ur help)

[Updated on: Mon, 05 March 2007 04:56]

Report message to a moderator

Re: listener running, but unable to listen client [message #222541 is a reply to message #222512] Mon, 05 March 2007 06:16 Go to previous messageGo to next message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

HI,
ora:012560:tns protocol adapter error


Are you check your Oracle DB on linux machine is start /open ?

conn sys as sysdba
startup

open your database and try to connect.


regards
Taj
Re: listener running, but unable to listen client [message #222605 is a reply to message #222541] Mon, 05 March 2007 11:03 Go to previous messageGo to next message
aboodlardy
Messages: 80
Registered: November 2006
Location: India
Member
Hi
Yes I have started the database. It is running. sitll i am getting the same error.
But when I tnsping from client, i am getting following output.

C:\DOCUME~1\SULEMAN>TNSPING 192.168.10.5(server i.e. linux)

TNS Ping Utility for 32-bit Windows: Version 9.0.1.1.1 - Production on 05-MAR-20
07 23:25:28

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

Used parameter files:

Used HOSTNAME adapter to resolve the alias
Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SID=*)(SERVICE_NAME=192.168.10
.5))(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.10.5)(PORT=1521)))
TNS-12560: TNS:protocol adapter error

C:\DOCUME~1\SULEMAN>

[Updated on: Mon, 05 March 2007 12:02]

Report message to a moderator

Re: listener running, but unable to listen client [message #222619 is a reply to message #222512] Mon, 05 March 2007 12:32 Go to previous messageGo to next message
BlackSwan
Messages: 25036
Registered: January 2009
Location: SoCal
Senior Member
While logged onto database server host, what get displayed from
$ lsnrctl status
Re: listener running, but unable to listen client [message #222668 is a reply to message #222619] Mon, 05 March 2007 20:15 Go to previous messageGo to next message
aboodlardy
Messages: 80
Registered: November 2006
Location: India
Member
Hi
On server where the database is. if i run lsnrctl status.
it gives me " command completed successfully".
that means lsnr is running.
help please.
Re: listener running, but unable to listen client [message #222673 is a reply to message #222512] Mon, 05 March 2007 20:58 Go to previous messageGo to next message
BlackSwan
Messages: 25036
Registered: January 2009
Location: SoCal
Senior Member
A whole lot more gets displayed than just "command completed successfully"; but you purposely chose to withhold this information that might contain valueable clues.
Since you think you know what is important, you can solve your own problem.
Your Own You're Own (YOYO)
Re: listener running, but unable to listen client [message #222677 is a reply to message #222668] Mon, 05 March 2007 22:14 Go to previous messageGo to next message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

Hi,
" command completed successfully".
Not just end line you should provide complete error stack.

lsnrctl status



regards
Taj
Re: listener running, but unable to listen client [message #222733 is a reply to message #222677] Tue, 06 March 2007 04:32 Go to previous messageGo to next message
aboodlardy
Messages: 80
Registered: November 2006
Location: India
Member
Sorry Taj,
I posted incomplete command output.
Here it is complete one.

LSNRCTL> status listener
Connecting to (DESCRIPTOR=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
----------------------
Alias listener
Version TNSLSNR for Linux: version 10.2.0.1.0-Production
Start Date 06-mar-2007 09:00:90
Uptime 0 days 0 hr. 0 min 24 sec
Trace Level 0ff
Security on : Local os authentication
SNMP off
Listener parameterfile /opt/app/network/admin/listener.ora
Listener logfile /opt/app/nerwork/log/listener.log
Listening Endpoints Summary..
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary....
Serviece "mydata" has 1 instace(s).
Instance "mydata" , status UNKNOWN, has 1 handler(s) for this service...
The command completed succesfully.
LSNRCTL>

sorry to anacedent too.
Re: listener running, but unable to listen client [message #222828 is a reply to message #222512] Tue, 06 March 2007 09:40 Go to previous message
BlackSwan
Messages: 25036
Registered: January 2009
Location: SoCal
Senior Member
>(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
The HOST= must be a hostname value that the client can resolve to (IP# or DNS resolveable)

[Updated on: Tue, 06 March 2007 09:40] by Moderator

Report message to a moderator

Previous Topic: Granting of role giving an error
Next Topic: TNS-12533: TNS:illegal ADDRESS parameters
Goto Forum:
  


Current Time: Sun Dec 04 12:35:58 CST 2016

Total time taken to generate the page: 0.13932 seconds