Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!enews.sgi.com!news-out.superfeed.net!propagator2-maxim!feed-maxim.newsfeeds.com!cyclone.bc.net!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: yong321@yahoo.com (Yong Huang) Newsgroups: comp.databases.oracle.server Subject: Re: High Version count in V$SQLAREA Date: 7 Jul 2003 11:46:06 -0700 Organization: http://groups.google.com/ Lines: 21 Message-ID: References: <1a68177.0307070450.410a4be1@posting.google.com> NNTP-Posting-Host: 192.94.8.250 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1057603567 1311 127.0.0.1 (7 Jul 2003 18:46:07 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 7 Jul 2003 18:46:07 GMT Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:237081 srivenu@hotmail.com (srivenu) wrote in message news:<1a68177.0307070450.410a4be1@posting.google.com>... > The following statements are coming from a client application. > Now my question is why are the version counts high for the above > statements even though they are using bind variables and no synonyms. > thanks in advance > regards > Srivenu Hi, Srivenu, James Morle's Scaling Oracle8i pp.278-9 gives the answer. In short, there're two cases where the same SQL has two versions (called two child cursors in Oracle documentation; I think James calls them two bodies of the same cursor head). One is when the bind threshold differs too much. Say :1 in the first version allows actual values of length 1 to 60 bytes, while in the second version :1 can accept values of length 61 and 200. The second case is when the optimizer plan changes. It can happen under various conditions. Yong Huang