12c: Extproc calls are not being released until listener is stopped and processes are killed
(Doc ID 2371611.1)
Last updated on JANUARY 20, 2025
Applies to:
Oracle Net Services - Version 12.1.0.2 and laterGen 2 Exadata Cloud at Customer - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.
Symptoms
You may find that extproc calls through the LISTENER (not Dynamically spawned ones) are not being released.
This can result in excessive processes remaining on the Database Server.
Only solution is to stop the Listener and kill the processes that seem to be "stuck"
Changes
This may be a new installation or an upgrade, containing SID_DESC information for Extproc rather than the default Extproc use via the Multithreaded Extproc Agent.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |