SQL Developer Holds On To Query Slaves where Parallelism is in use
(Doc ID 1467105.1)
Last updated on APRIL 04, 2019
Applies to:Oracle SQL Developer - Version 3.0 to 4.1 [Release 3 to 4]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
When a query is executed that makes use of parallelism the issue is that the SQL Developer sessions using JDBC retain query slaves rather than releasing them for re-use by other sessions.
For example after running a Query that fetches some rows issue the following in SQLDeveloper
You will be able to note that the State column will show up as Waiting which means that the JDBC has held up the Query session.
Bug 14066829 - SQL DEVELOPER USING JDBC HOLDS ON TO QUERY SLAVES has been logged to address this which was eventually closed as Not a Bug
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