OO4O Does Not Immediately Close The Session Object In A .NET Environment
(Doc ID 1264478.1)
Last updated on FEBRUARY 22, 2019
Applies to:
Oracle Objects for OLE - Version 8.1.7.0 to 11.2.0.2 [Release 8.1.7 to 11.2] Microsoft Windows (32-bit)
Symptoms
You set the OraDatabase object to Nothing in your Oracle Objects for OLE (OO4O) application running in a .NET environment, execute that line of code and then check V$SESSION for existing sessions. The OO4O session from your application is still present. In a VB 6 environment the session would have been released and it would not have been visible in V$SESSION after executing the same line of code.
Changes
Resources are released at different times when similar code is run under a VB 6 vs. a VB.NET environment.
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!