This content has been marked as final. Show 1 reply
You can call OracleConnection.ClearPool or ClearAllPools to reset the connection pool without restarting the driver.
I'm not sure if the trace file would help you diagnose. It's not an error to have a connection indefinitely open per se. If no errors are being thrown, tracing will be of limited help.
I assume you are disposing all your OracleConnection objects explicitly. Is it possible some corner case occurs where Dispose isn't called, such as a corner case or a procedure that exits abnormally? Could it be possible that the DB is getting bounced on occasion and the app doesn't exit, but continue to hold onto the "dead" connection? I can't really answer these questions without knowing how your app handles these scenarios.