ORA-609

ORA-609 is an error message that you may see as a result of timeout issues. In this case, no modification to the actual code is needed; instead, you must examine the connection and figure out what may be triggering the timeout.

The Problem

When facing ORA-609, you will see the following error message:

ORA-609: opiodr aborting process unknown ospid

The error indicates that a client connection has failed to complete or that the connection was aborted without being successfully connected. This happens when the 60-second default timeout passes or is triggered when the database session is aborted from the operating system prompt.

The Solution

To resolve this error, you must increase the values for INBOUND_ CONNECT_ TIMEOUT on both the listener side and the server side. If you are getting ORA-609 because of a connection timeout issue, increasing the values should fix the problem. You should change INBOUND_ CONNECT_ TIMEOUT to read as the following:

Sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=180

Listener.ora: INBOUND_CONNECT_TIMEOUT_listener_name=120

Above, the timeout seconds are being set to 120 in place of the default 60. While this simple change should fix most ORA-609 errors, if you continue to see this error then you should try to locate which client is causing the error. Set the sqlnet.ora file parameter to

sqlnet.ora file: DIAG_ADR_ENABLED = OFF

and reload the listener. Take a look at the PROGRAM and HOST fields to make sure that the timestamps of the sqlnet.log and alert.log errors are the same. After locating the client causing the error, you can enable client tracing. For client tracing assistance, consider contacting an Oracle expert or customer service provider.

You can also take a look at the listener.log to find timestamps that match the ORA-609 error in the alert.log. Again, once you locate the client causing the error, you can enable client tracing.

Looking Forward

Resetting the INBOUND_ CONNECT_ TIMEOUT should fix or at least reduce the chances of seeing error ORA-609. If you are unable to resolve the error by increasing the timeout seconds, you may want to contact your database administrator or Oracle consultant to resolve the issue. Locating and fixing the client causing the error may not be something that programmers who are just beginning to code can fix on their own. As always, check the credentials and certifications of the Oracle consultant before accepting services.

STILL HAVE QUESTION?

Submit your question