After session object is set to NULL, still the oracle processes are in memory, never cleaned up. Does require any special methods to kill the process.
dbObject.Close(); // called
dbSession = NULL ; // set session object to null
Oracle processes are still in memory and crashes server.
Using Oracle ver 8.1.7/OO4O 3.15
What is wrong here?
Anyone came across similar issues..
Have you tried to remove all OraParameters after stored procedure call and before assigning null to session?
Otherwise there may be circullar references between OraDatabase and OraParameter causing memory leak after releasing your reference to OraSession.