Ora 609 ошибка

ORA-609 : OPIODR ABORTING PROCESS UNKNOWN OSPID
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

          ORA-609 with
TNS-12537: TNS:connection closed

We almost time receive an error such as ora-609 which shows
in alert log as

TNS- TNS-12537: TNS:connection closed
        ns secondary err code: 12560
        nt main err code: 0
        nt secondary err code: 0
        nt OS err code: 0
    opiodr aborting process unknown ospid (12345) as a result of
ORA-609

This error means could not attach to incoming
connection, so our database process was aborted or closed because incoming
connection was not passed to it by listener. In our case we found sqlnet error
stack as shown below

 TNS-12537: TNS:connection
closed

It means the dedicated process didn’t have a client connection
anymore to work.

As we all know the process of client connections:

1. First
Client initiates a connection to the
database so it connects to the listener.

2. Then
listener starts a dedicated DB process that will receive this connection or
session.

3. After
that, this dedicate process is started and listener passes the connection from
the client to this process.

4. Then
the sever process takes the connection from the listener to continue the
handshake with the client.

5. After
that Server process and client exchange messages or information required for
establishing a session or user logon.

6. Then
the session is opened now.

In
our case, it may be when the dedicated process tries to communicate with the
client it finds that connection was closed.

Solution or
Work around:

We
can eliminate this error by increasing the value of SQLNET.INBOUND_CONNECT_TIMEOUT
in sqlnet.ora file. 

By default the SQLNET.INBOUND_CONNECT_TIMEOUT value is 60
seconds.

The
sqlnet.ora file can be found in RDBMS_HOME/network/admin.

For example:

$ cd $ORACLE_HOME/network/admin

$vi sqlnet.ora

And change the value of SQLNET.INBOUND_CONNECT_TIMEOUT as:

SQLNET.INBOUND_CONNECT_TIMEOUT=300

Then
save the file.

There are many more possibilities which can cause this error
such as:

1. This can happen suppose our client closed the
connection immediately after initiating it.

2. This may occur
when firewall kill the connection.

3. Sometimes, it may happen because of Database, OS or network
performance problem.

4. This error may occur when some client crashes.

Hope this may also useful here:

Hope this may useful and helpful.
Please let us know for any concerns either by below comments or write to @contact us: https://ora-data.blogspot.in/

Regards,
ora-data Team

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]

·         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:

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.

Expected
Fix :

I am running a batch java application. The application runs every 10/20 minutes in my Production and UAT environment and I get database alerts like this:

Thu Feb 06 15:15:08 2014
opiodr aborting process unknown ospid (28246400) as a result of ORA-609

After researching a bit on the internet the suggested fix for these alerts is to change INBOUND_CONNECT_TIMEOUT as:

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

We have changed the setting on the database server side but don’t know where to change in the client application. We are using c3p0 to create a connection pool and we are setting only these parameters:

dataSource.setAcquireRetryDelay(30000); 
dataSource.setMaxPoolSize(50);
dataSource.setMinPoolSize(20);
dataSource.setInitialPoolSize(10);

We have other web services running on the same server as the batch application and they use Tomcat’s DBCP pool and they don’t seem to create any alerts. Also strangely enough, our batch application doesn’t generate the alerts in lower test environments. They happen once in a while but the UAT and PROD environments get these alerts very frequently based on the schedule. Any suggestions what configurations to set in the c3p0 pool or should I try changing to another pool API like DBCP?

Update: I have added a few more parameters in the datasource and the frequency of alerts has reduced. I added the following and the number of alerts have gone down from 15 an hour to 4 an hour.

dataSource.setLoginTimeout(120);
dataSource.setAcquireRetryAttempts(10);
dataSource.setCheckoutTimeout(60000);