Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Performance implication of many open "statement handles"

Re: Performance implication of many open "statement handles"

From: Anurag Varma <avarmadba.skipthis_at_yahoo.com>
Date: Sat, 10 May 2003 17:51:14 GMT
Message-ID: <m_ava.1538$tc5.1517@nwrdny03.gnilink.net>

"Frank Foss" <fozzie_beer_at_hotmail.com> wrote in message news:b9hb7r$je2ld$1_at_ID-190416.news.dfncis.de... -snip-
> Now, the question:
> Can similar operations: Prepare once, execute many times, be done in
> C++/OCI? (Sorry if that's a stoopid question)

Perl DBI uses OCI to do its thing so I guess you would know what the answer is.
Look at the source code of DBD:Oracle and you can see how it does its thing.

> What are the consequences, in terms of resources used on the Oracle
server,
> of having lots of "prepared, and open" handles in the application for a
long
> (hours/days) time? Is it only entries in the shared_pool, and get groomed
> out if not referenced for a long time?
> Should the prepared handles be closed shortly after use, and
> re-prepared(triggering a soft parse in the server), or is it OK, to not
> close them until the application closes?

imho its ok to close them once you are done with them.

Anurag
>
> Thanks for reading so far, got a little long,
> Foz
>
>
Received on Sat May 10 2003 - 12:51:14 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US