Help with diagnosing trace of listener
Hi,
Customer complains about "socket timeouts" so I have enable tracing on the listener (not sure if the db is to blame), running
trcasst -e1 filename
I see this:
2019-05-10 12:36:26.694 : ntprd:exit
2019-05-10 12:36:26.694 : nsbequeath:NSE=12586
2019-05-10 12:36:26.694 : nsbequeath:error reading REDIR/NSE msg
2019-05-10 12:36:26.694 : nserror:entry
2019-05-10 12:36:26.694 : nserror:nsres: id=5, op=72, ns=12586, ns2=0; nt[0]=0, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
According to:
Oracle Net Listener Trace shows NSE=12586, is This an Error ? (Doc ID 738724.1)
Is not an error, but what about this:
2019-05-10 11:12:02.149 : nserror:nsres: id=6, op=76, ns=12534, ns2=12560; nt[0]=504, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
2019-05-10 11:12:02.149 : ntprd:entry