My Oracle Support Banner

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

Last updated on FEBRUARY 10, 2022

Applies to:

JDBC - Version and later
Oracle Database - Enterprise Edition - Version and later
Oracle Net Services - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.


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:

[<Time Stamp>] nsprecv: reading from transport...
[<Time Stamp>] nttrd: entry
[<Time Stamp>] nttrd: exit
[<Time Stamp>] ntt2err: entry
[<Time Stamp>] 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


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.