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

Home -> Community -> Usenet -> c.d.o.server -> Re: High reloads by SYS?! large shared_pool_size.. was Re: where are all these hard parses coming from?

Re: High reloads by SYS?! large shared_pool_size.. was Re: where are all these hard parses coming from?

From: Mark D Powell <Mark.Powell_at_eds.com>
Date: 6 Apr 2003 10:27:52 -0700
Message-ID: <2687bb95.0304060927.cc04ff3@posting.google.com>


"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:<b6ovcv$qgg$1$8300dec7_at_news.demon.co.uk>...
> Comments inline
>
>
> Do you have multiple children in v$sql for each statement ?
> When using proper bind variable techniques, I believe that
> if the maximum size of the bind variable changes significantly
> between callls, then a new child cursor has to be created and
> is therefore subject to a hard parse, and some programming tools
> set the maximum size to the actual size automatically. Is it
> possible that this might be related in some way to your problem -
> viz. using more memory that expected, therefore causing more
> reloads than expected.

This might explain why we have child cursors for sharable SQL that Oracle support said should not have children while they were trying to help us trace down what they acknowledged was a library cache space management bug that was never resolved. And it makes me wonder if we were locked into looking at the wrong area.

Received on Sun Apr 06 2003 - 12:27:52 CDT

Original text of this message

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