Hi,
So we intermittently get this error which is more of a nuisance.
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Solaris: Version 19.0.0.0.0 - Production
Oracle Bequeath NT Protocol Adapter for Solaris: Version 19.0.0.0.0 - Production
TCP/IP NT Protocol Adapter for Solaris: Version 19.0.0.0.0 - Production
Version 19.14.0.0.0
Time: 17-OCT-2022 07:18:10
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12608
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=[IP_ADDRESS])(PORT=30109))
Mon Oct 17 07:19:07 2022
TT02 (PID:648): Attempting LAD:2 network reconnect (12608)
TT02 (PID:648): LAD:2 network reconnect abandoned
TT02 (PID:648): Error 12608 archiving LNO:2 to '[TNS_ALIAS_DR]'
ORA-16038: log 2 sequence# 895779 cannot be archived
Log a call with Oracle Support. Had increased most timeout settings that we can think of TransportLagThreshold, TransportDisconnectedThreshold and ArchiveLagTarget. ReopenSecs is at 300. Can't change NetTimeout as we are using ASYNC and increase INBOUND_CONNECT_TIMEOUT also on sqlnet.ora and listener.ora and still getting this error.
We know the database/server can be busy at certain time of the day due to supplemental logging+logmining so we kinda expected these. We just really want to increase whatever other timeout settings somewhere but we can't find what other settings control this timeout.
Now, Oracle Support says run tnsping and trcroute whenever you get this error and am so crushed. Not sure if the engineer is joking. They didn't even provide a script of sort, just say run tnsping and trcroute every 30 sec for a period of time when you get the error. Aaargghhh. Obviously, we can't have anyone 24x7 to monitor for error and fire up tnsping and trcroute because the error happens on various times of the day. I would have thought they will be more helpful to provide a script to run. Don't think any tracing will help either.
Anyway, is there anyone who has this issue before and knows what timeout settings can be increase so the disconnect doesn't happen? Personally, I don't really mind getting the disconnects and treat them as per normal. If I increase the timeout and goes fine for a month and then happens again after, I don't want to be increasing it again. But my fellow DBAs,- they have another opinion about it :( I suppose if we can come up with a value so that the disconnect permanently disappears then that is an acceptable solution. Unfortunately, if Oracle Support don't know, what's next? Hence this post? :-)