opiodr aborting process unknown ospid
as a result of ora-609
opiodr aborting process unknown ospid as a result of ora-609
TNS-12560: TNS:protocol adapter error
ORA-609 : opiodr aborting process unknown ospid (2230_87567)
ORA-609 : opiodr aborting process unknown ospid (2230_87567)
· Details
on the ORA-609 error, see MOSC note 1121357.1.
As a general error, the ORA-609 error indicates that a client connection failed to complete. This can be an ORA-609 from an abort or killing an Oracle session.
To diagnose any error, you start by using the OERR
UTILITY to display the ORA-609 error:
Example :
bash-3.2$ oerr ora 609
00609, 00000, "could not attach
to incoming connection"
// *Cause: Oracle process
could not answer incoming connection
// *Action: If the situation
described in the next error on the stack
//
can be corrected, do so; otherwise contact Oracle Support.
The ORA-609 error is thrown when a client connection
of any kind failed to complete or aborted the connection process before the
server process was completely spawned. Beginning with 10gR2, a default value
for inbound connect timeout has been set at 60 seconds. This is also
triggered when a DB session is killed/aborted manually from the OS prompt.
Solution:
Solution:
Increase the values for INBOUND_CONNECT_TIMEOUT at
both listener and server side sqlnet.ora file as a preventive measure.
If the problem is due to connection timeouts, and
increase in the following parameters should eliminate or reduce the occurrence
of the ORA-609 error.
ü Sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=180
ü Listener.ora:
INBOUND_CONNECT_TIMEOUT_listener_name=120
ORA-12560: TNS: protocol adapter error
Cause: A generic protocol adapter error occurred.
Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and re-execute the operation. Turn off tracing when the operation is complete.
Cause: A generic protocol adapter error occurred.
Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and re-execute the operation. Turn off tracing when the operation is complete.
Expected
Fix :
1.
Check
environment variable like $ORACLE_HOME, $PATH, $ORACLE_BASE
2.
TNS_ADMIN
is set properly
3.
Verify
firewall that not blocking ports
4.
Check
permission
No comments:
Post a Comment