Unfortunately, I am not running OPS or RAC.
This is a failover-cluster -- if the primary node goes down, the
database instance
is started on the secondary node.
I think Tanel is right that sqlnet.expire_time wouldn't apply.
However, Tanel, I didn't understand the paragraph
Also, sqlplus is
Hi!
Actually it seems that as long as the network (TCP) connection is up at OS
level, Oracle is just gonna wait for reply for it's packets sent. So,
probably no 3113 error before OS drops the TCP connection (if sqlplus or OCI
doesn't have some kind of timeout implemented). Sorry about
I'm sorry, but I really can't remember how an Oracle SQLPlus client is supposed
to behave when the database server's network interface is pulled out.
We were testing a new Sun Cluster and tests for Storage FC Path Failure,
Instance Failure,
Node Failure, HeartBeat failure and single Network
Hemant,
You are right it does get a timeout from the TCP stack, but the default
for the connection timeout is 30 minutes. There is a sqlnet parameter where you
can modify the timeout to make it shorter (sqlnet.expire_time?) Check metalink
note 151972.1 for more info.
HTH
Mike
Hi!
This sqlnet.expire_time affects server, not sqlplus itself AFAIK. The issue
is likely, that sqlplus has sent a sqlnet request to server, but hasn't got
any response since you pulled the network cable. Thus it'll wait until TCP
connection gets timeout.
Also, sqlplus is different from normal
I agree sqlnet.expire_time does only effect the server, but normally when the
server kills the connection the client side will drop. But in this case it
won't because there is no network for the client to get the dead connection
timeout from the server. It sounds like Hemant is running OPS
