ORA-0609 Errors in Database Alert Log When Running JDBC Application Jobs (Doc ID 1269137.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2]
Oracle Net Services - Version to [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 10-Oct-2013***


After upgrading the database from to, the following error messages are intermittently reported in the database alert log :
opiodr aborting process unknown ospid (16127) as a result of ORA-609

The application executed consists of cron jobs using JDBC thin 10.2 for connection to the database.

Server trace file, upon attempting to communicate with the client side, sees an unexpected EOF occurring on the database side of the connection:

[000001 04-NOV-2010 17:41:03:550] nsprecv: reading from transport...
[000001 04-NOV-2010 17:41:03:550] nttrd: entry
[000001 04-NOV-2010 17:41:03:556] nttrd: exit
[000001 04-NOV-2010 17:41:03:556] ntt2err: entry
[000001 04-NOV-2010 17:41:03:556] ntt2err: Read unexpected EOF ERROR on 14

Although the database is reporting ORA-0609 messages indicating an aborted connection attempt, there is no reported error at the application side.


Upgrade of database from to


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms