Thursday, 28 June 2018

ORA-609 : opiodr aborting process unknown ospid


When a client makes a connection with Oracle Database, there are multiple steps involved. These steps do multiple network trips between the client and the server. The parameters that we are using here are basically hiding a problem in the network from the application . These parameters control when Oracle will throw an error about connections not getting completed. Please do ask your network team to look into network issues.


ORA-609 : opiodr aborting process unknown ospid

Cause:

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:

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,an increase in the following parameters should eliminate or reduce the occurrence of the ORA-609s.

Sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=180
Listener.ora: INBOUND_CONNECT_TIMEOUT_listener_name=120


For more details -- refer to metalink note [ID 1121357.1]

No comments:

Post a Comment