My Oracle Support Banner

When are New Cached Connections Created after Database Sessions are Killed and ORA-00028 Occurs? (Doc ID 434089.1)

Last updated on SEPTEMBER 24, 2019

Applies to:

JDBC - Version 10.2.0 and later
Information in this document applies to any platform.

Goal

All the database sessions for the connections in a connection cache are killed. Then the application gets an invalid connections from the cache. When the application tries to use the connection an "ORA-00028: your session has been killed" error occurs. You expect this ORA-00028.

However when the application gets another connection and tries to use it another ORA-00028 occurs. You expected a new, good connection - not a second ORA-00028.

Solution

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
Goal
Solution
 [1] Overview
 [2] KilledSessions.java - source code
 
[3] sess.sql - script to kill database sessions and query database sessions
 
[4] Output from KilledSessions
 [5] Output from sess.sql and querying database sessions as KilledSessions runs
 [6] Explanation of output in [4] and [5]
 [7] Output from KilledSessions modified to not display ORA-00028
 [8] MinLimit does not create new connections
References

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