Re: So, no one is man enough to answer my Oracle question?

Hi,

Just one suggestion :
When you are removing parameters from your collection check the OResult. I think the parameter is not being removed. Possible reason may be you are calling m_pDatabase.GetParameters().Remove("LIST_CURSOR"); in both success and failure instead of params.Remove("LIST_CURSOR");. I think you should remove it from params collection.

Thanks to you

Asif Hasan
Spectrum Engineering Consortium Ltd.

In article <7g1aki$seq$1_at_news.netvision.net.il>,   "Yaron" <yadler_at_hypernix.co.il> wrote:
> Dear All,
> I have posted the following quwestion twice already, and got no responce.
> I wonder if there isn't anyone from this Oracle community that knows Oracle
> good enough to answer?
>
> So here it goes again:
>
> While working with Oracle objects for OLE (version 2.3.2.2.0) I
> encounter this problem:
> After declaring an OSession object and ODatabase object, I tried to run
> the following lines of code continuously.
> I discovered that the computer's (oracle client) memory increasing
> consistently (to enormous sizes).
> These kind of memory leak occures only when using OTYPE_CURSORparameters !
>
> Example code:
>
> OParameterCollection params = m_pDatabase.GetParameters();
> params.Add("LIST_CURSOR",NULL,OPARAMETER_OUTVAR,OTYPE_CURSOR);
> if (m_pDatabase.ExecuteSQL("begin SqlQuery(:LIST_CURSOR); end;") !=
> OSUCCESS)
> {
> m_pDatabase.GetParameters().Remove("LIST_CURSOR");
> return;
> }
> m_pDatabase.GetParameters().Remove("LIST_CURSOR");
>
> It is obvious that the oracle client was supposed to free the memmory
> allocated in this operation, but it doesn't.
>
> Did any of you encountered this problem before?
> How did you solve it?
>
> Please help
> Yaron Adler
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Tue Apr 27 1999 - 02:16:12 CDT