TNS FATAL ERROR

Question

We are getting following error in alert log file Can one suggest
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for HPUX: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.1.0.6.0 - Production
TCP/IP NT Protocol Adapter for HPUX: Version 11.1.0.6.0 - Production
Time: 13-AUG-2012 16:40:04
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: <unknown>
ORA-609 : opiodr aborting process unknown ospid (3936_1)
Mon Aug 13 16:50:58 2012

Answer 1

947721 wrote:
We are getting following error in alert log file Can one suggest Insufficient data. The errors listed in the snippet you posted:
12535, 00000, "TNS:operation timed out"
// *Cause: The requested operation could not be completed within the time out
// period.
// *Action: Look at the documentation on the secondary errors for possible
// remedy. See SQLNET.LOG to find secondary error if not provided explicitly.
// Turn on tracing to gather more information.
12606, 00000, "TNS: Application timeout occurred"
// *Cause:  A network session did not reach an application-defined stage
//          within the allowed time interval.
// *Action: This is an error which does not normally appear at the high level.
//          The action to take is application specific, and is detailed in the
//          higher level error description.Enable client SQL*Net tracing to troubleshoot the problem.