solaris 2.6+oracle7.3.4
最近两天，oracle的监听进程连续死掉，查看listener.trc文件
最后一段为
valid node check on incoming node XXX.XXX.XXX.XXX
Accepted Entry: XXX.XXX.XXX.XXX
transport is open
Reading parameter "sqlnet.authentication_required" from parameter file
Parameter not found
Using default value "FALSE"
Counting # of items in "sqlnet.authentication_services" parameter
Parameter not found
Found 0 items
Using default value "all available adapters"
Reading parameter "SQLNET.ENCRYPTION_SERVER" from parameter file
Parameter not found
Using default value "ACCEPTED"
Counting # of items in "SQLNET.ENCRYPTION_TYPES_SERVER" parameter
Parameter not found
Using default value "all available algorithms"
Reading parameter "SQLNET.CRYPTO_CHECKSUM_SERVER" from parameter file
Parameter not found
Using default value "ACCEPTED"
Counting # of items in "SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER" parameter
Parameter not found
Using default value "all available algorithms"
global context check-in (to slot 4) complete
doing connect handshake...
50 bytes from transport
got NSPTCN packet
recving connect data
前两天刚好在
http://www.oraclefan.net/ubb/Arc ... 枋龅囊恢智榭龊芟嗨?/a>
When a client sends it's connect data, if the
total packet length is greater than 230 bytes, SQL*Net on the client will
break up the packet into 2 pieces: a 50 byte connect packet, and a second packet
continuing connect data. When a client sends the connect request to a TNS
listener, a procedure called nsanswer() is invoked. When nsanswer() gets the
connect packet, the listener will wait in a blocking mode for the connect
data to arrive. Usually, the connect data arrives after the 50 byte connect
packet. The question is, what happens to the listener if the connect data
never arrives? As an example, imagine that at connect time with a Windows 95
application, the application GPFs, but just before the GPF, a 50 byte connect
packet left the client. The listener s nsanswer() is invoked, and is now
waiting for connect data. Connect data never arrives because of the GPF on
the client. What happens to the listener? The listener is "hung" in a read
state forever waiting for connect data.
请各位大侠看看我的监听死掉是不是这种原因，
如果是有可能是什么原因导致的，应该如何开始调查？
能不能解释一下listener.trc文件中各行都是什么意思呀？
 |
