Client-side Memory leak while executing PL/SQL and reading from a view

Question

Iam noticing memory leaks in OCCI while performing the following:
Sample function()
1. Obtain a connection
2. Create a statement to execute a PL/SQL procedure
3 Execute the statement created in step #2
4. Terminate the statement created in step #2
5. Create a statement to read from a view which was populated
by executing stored procedure in step #3
6. Execute the statement created in step #5
7. Terminate the statement created in step #5
8. Release the connection
The PL/SQL populates a view with fixed 65,000 records for every execution. PL/SQL opens a cursor, loads 65000 records and populates the target view and closes the cursor at the end. If i invoke the above function it results in memory leak of 4M for every call. I tried several variants such as:
1. Disabling statement caching
2. Using setSQL instead of newly creating second SQL statement
3. Obtaining two separate connections for these two activities (PL/SQL exec and View read)
4. Breaking the sample function into two, one for each of these activities (PL/SQL exec and View read).
All the combinations results in the same behaviour of 4M memory leak.
Iam using Oracle 10g Client/Server 10.2.0.1.0.
Is there any known limitations in this area?

Answer 1

Yes. Iam closing the result set and terminating the statement.
My program contains layers of inhouse wrapper classes, which will take some time for
me to present it in pure OCCI calls, to be posted here for your understanding.
After some more debugging, i found that if the connection level statement caching is set to
0, the memory leak is much lower than before.
Thanks.
Message was edited by:
user498920