Home » RDBMS Server » Networking and Gateways » TNS protocol adapter error (oracle 9i server on windows xp professional and clien on winxp home edition)
TNS protocol adapter error [message #289526] Sun, 23 December 2007 11:28 Go to next message
vishal_nitj04
Messages: 3
Registered: December 2007
Junior Member
Hello everyone!!
I am trying to connect to oracle server from client but it is giving tns protocol adaptor error .I am using localnaming and has put direct ipaddress instead of hostname.ping utility and tnsping are working from client side.from server machine database is being accessed.Below is the listener trace file.Kindly view the .trc file below and help me out.
Thanks in advance

listener.trc file...

nsdo: cid=3, opcode=67, *bl=80, *what=10, uflgs=0x0, cflgs=0x3
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=2, flg=0x4204, mvd=0
nsdo: gtn=202, gtc=202, ptn=10, ptc=8163
nscon: sending NSPTRF packet
nspsend: plen=92, type=4
ntnwr: failed to write 92 bytes
ntn2err: entry
ntn2err: error: handle=232, op=6, nt[0]=524, nt[1]=997
ntn2err: exit
nsdo: nsctxrnk=0
nsrah: reading (asynchronously) from transport...
nsrah: ...into overflow area...
ntnrd: failed to read 2064 bytes
ntn2err: entry
nstimarmed: no timer allocated
nsdo: cid=3, opcode=66, *bl=0, *what=0, uflgs=0x0, cflgs=0x2
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=2, flg=0x4200, mvd=0
nsevunreg: cid=3, sgt=0, rdm=2
nsrah: re-setting transport read mode
nsevunreg: 2 registered connection(s)
nsdo: nsctxrnk=0
nsclose: closing transport
ntndisc: entry
sntndisc: Error: Inconsistent trace parameters line: 13605708
ntndisc: exit
nsclose: global context check-out (from slot 3) complete
nsmfr: 2312 bytes at 0xd98db8
nsmfr: 476 bytes at 0xd9a280
nsevwait: 2 registered connection(s)
nsevwait: 0 pre-posted event(s)
nsevwait: waiting for transport event (0 thru 2)...
Re: TNS protocol adapter error [message #289532 is a reply to message #289526] Sun, 23 December 2007 12:05 Go to previous messageGo to next message
BlackSwan
Messages: 25033
Registered: January 2009
Location: SoCal
Senior Member
Too bad you decided to NOT post actual error code.

Does the following help any?
http://www.cryer.co.uk/brian/oracle/ORA12560.htm
Re: TNS protocol adapter error [message #289533 is a reply to message #289532] Sun, 23 December 2007 12:10 Go to previous messageGo to next message
vishal_nitj04
Messages: 3
Registered: December 2007
Junior Member
sorry for that..
this is ora-12560 and ora-12535 error.
no this link doesnot work.
Re: TNS protocol adapter error [message #289534 is a reply to message #289533] Sun, 23 December 2007 12:40 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
It works for me and describe useful informations and solution.
I'm pretty sure it is not the only site to descrive this but you can only find them if you use, for instance, Google.

Regards
Michel
Re: TNS protocol adapter error [message #289535 is a reply to message #289526] Sun, 23 December 2007 12:44 Go to previous message
BlackSwan
Messages: 25033
Registered: January 2009
Location: SoCal
Senior Member
12560, 00000, "TNS:protocol adapter error"
// *Cause: A generic protocol adapter error occurred.
// *Action: Check addresses used for proper protocol specification. Before
// reporting this error, look at the error stack and check for lower level
// transport errors. For further details, turn on tracing and reexecute the
// operation. Turn off tracing when the operation is complete.
</a/oracle:> oerr ora 12535
12535, 00000, "TNS:operation timed out"
// *Cause: The requested operation could not be completed within the time out
// period.
// *Action: Look at the documentation on the secondary errors for possible
// remedy. See SQLNET.LOG to find secondary error if not provided explicitly.
// Turn on tracing to gather more information.


post contents of sqlnet.ora & tnsnames.ora files from CLIENT

use CUT & PASTE to show whole session showing what you are doing & how Oracle responds.
Previous Topic: ORA-12154: TNS:could not resolve service name
Next Topic: Basic networking
Goto Forum:
  


Current Time: Sat Dec 03 01:15:01 CST 2016

Total time taken to generate the page: 0.09873 seconds