Re: SCO Oracle 7 and SQL*Net V2

From: Rey Tacdol <reyt_at_ngc.com>
Date: Wed, 21 Dec 1994 22:03:51 GMT
Message-ID: <D16pyK.5IL_at_ngc.com>


In article <3cv21j$m1o_at_ionews.io.org>, <lschan_at_io.org> writes:
> I am attempting to install SQL*Net V2 on a SCO ODT system with a client
> windows work station running SQL*Net Client for Windows V2. I am having
> problems configuring the TNS listener process. I have attached a trace
> for the startup of the listener process, and I would appreciate if
> someone can identify the configuration problems from this trace since
> it is not documented in the Oracle manuals.
>
>
> ---------------------- Trace file ------------------------------------
>
> TNSLSNR for AT&T System V/386: Version 2.1.3.0.0 - Production on
> 17-DEC-94 00:01:42
>
> Copyright (c) Oracle Corporation 1994. All rights reserved.
>
>
> --- TRACE CONFIGURATION INFORMATION FOLLOWS ---
> New trace stream is "/u/u01/home/dba/oracle/product/7.1.3/network/trace/listener.trc"
> New trace level is 6
> --- TRACE CONFIGURATION INFORMATION ENDS ---
>
> --- PARAMETER SOURCE INFORMATION FOLLOWS ---
> Attempted load of system pfile source /etc/listener.ora
> Parameter source loaded successfully
>
> Attempted load of command line source
> Parameter source was not loaded
>
> -> PARAMETER TABLE LOAD RESULTS FOLLOW <-
> Successful parameter table load
> -> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <-
> STARTUP_WAIT_TIME_LISTENER = 0
> SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = CCSP)
> (ORACLE_HOME = /u/u01/home/dba/oracle/product/7.1.3)))
> CONNECT_TIMEOUT_LISTENER = 10
> TRACE_LEVEL_LISTENER = ADMIN
> PASSWORDS_LISTENER = (passw)
> LISTENER = (ADDRESS_LIST = (ADDRESS= (PROTOCOL= IPC)
> (KEY=orasrv.world)) (ADDRESS= (PROTOCOL= IPC) (KEY= CCSP))
> (ADDRESS = (COMMUNITY = GO_ORACLE.world) (PROTOCOL = TCP)
> (Host = ccs) (Port = 1525)))
>
> --- PARAMETER SOURCE INFORMATION ENDS ---
>
> --- LOG CONFIGURATION INFORMATION FOLLOWS ---
> Log stream will be
> "/u/u01/home/dba/oracle/product/7.1.3/network/log/listener.log" Log stream
> validation requested Log stream is valid
> --- LOG CONFIGURATION INFORMATION ENDS ---
>
> (ADDRESS=(PROTOCOL=beq))
> No process parameters set
> inheriting the connection...
> opening transport...
> NT layer IPC connection has been established.
> transport is open
> global context check-in (to slot 0) complete
> doing connect handshake...
> 169 bytes from transport
> got NSPTCN packet
> discarding connect data (135 bytes)
> connection inherited
> connected
> Resolved "CONNECT_TIMEOUT_LISTENER" to: 10
> Resolved "STARTUP_WAIT_TIME_LISTENER" to: 0
> (DESCRIPTION=(CONNECT_TIMEOUT=10)(ADDRESS=(PROTOCOL=IPC)
> (KEY=orasrv.world)))
> KEY = orasrv.world
> opening transport...
>
> -<ERROR>- sd=-1, op=3, resnt[0]=530, resnt[1]=97, resnt[2]=0
> -<ERROR>- nsres: id=0, op=65, ns=12560, ns2=0; nt[0]=530, nt[1]=97, nt[2]=0
> -<ERROR>- unable to open transport
> Deallocating cxd 0x429560.
> -<ERROR>- Reporting the following error stack:
> TNS-12560: TNS:protocol adapter error
> TNS-00530: Protocol adapter error
> AT&T System V/386 Error: 97: Protocol not supported
> sending NSPTRF packet
> 12 bytes to transport
> sending 512 bytes connect data
> 512 bytes to NS buffer
> no timer allocated
> 522 bytes to transport
> closing transport
> global context check-out (from slot 0) complete
>

Lon,
I hope you have solved your problem by now. If you haven't or if you can reproduce the condition, I would appreciate it very much if you can send me a Network General Sniffer trace of your problem. My contact at Oracle and I have been trying for a few days now to obtain a real life TNS Refuse packet and so far we have limited success. The Sniffer trace of your problem will be used in testing the new NGC Sniffer software that decodes the TNS protocol.

The error TNS-12560 that you are getting is a failure of the NS to grant one or more of the protocol characteristics or global service options specified in the TNS Connect packet. This error happens to be one of a few error types not normally visible to the user. In your case, it looks like the problem is in the requested protocol characteristics as the Error 97 suggests.

Hope to hear from you soon.

Rey Tacdol
Software Engineer
Network General Corporation
4200 Bohannon Drive
Menlo Park, CA 94025
(415) 473-2000 Received on Wed Dec 21 1994 - 23:03:51 CET

Original text of this message