DG4ODBC Process Remains After Oracle Session Has Terminated
(Doc ID 1326989.1)
Last updated on JANUARY 18, 2017
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
After terminating a session which is using DG4ODBC to connect to SQLBASE, the process DG4ODBC is staying in memory.
After a while, there are too many open processes (DG4ODBC) an RAM consumption is too high.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|