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 hard parse and version counts for dbms_lob functions

Re: High hard parse and version counts for dbms_lob functions

From: El Toro <medawsonjr_at_yahoo.com>
Date: 5 May 2003 22:12:27 -0700
Message-ID: <2e1cd2b.0305052112.663e21fc@posting.google.com>


> While I'm aware of the 8.1.5 bug with timed_statistics=true, I notice in the
> same tkprof output that all other SQL that makes use of bind vars (e.g.,
> select, insert, update, delete) parses once and executes many.
>
> Is there anything that I'm missing here? Should this be so for the dbms_lob
> package functions? Is this to be expected if LOBS are used such that they are
> stored out-of-line from the table and in a separate LOB segment?

It looks like this may be another bug that I'm hitting, which deals with the default setting of _sqlexec_progression_cost in 8.1.5 through 8.1.6.2 (and possibly higher). This parameter controls what sessions get tracked in v$session_longops, and can cause high version count issues as well. Even Oracle Applications mandates that this hidden parm be set to '0'. Received on Tue May 06 2003 - 00:12:27 CDT

Original text of this message

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