ORA-0609 Errors in Database Alert Log When Running JDBC Application Jobs
Last updated on OCTOBER 12, 2017
Applies to:JDBC - Version 10.2.0.1 and later
Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Oracle Net Services - Version 220.127.116.11 and later
Information in this document applies to any platform.
After upgrading the database from 10.2.0.4 to 18.104.22.168, 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 10.2.0.4 to 22.214.171.124.
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