Since v$sqlarea is an aggregate of v$sql, there
has to be a mechanism for reporting something
when different child cursors (i.e. the v$sql entries)
are running under different optimizer modes. That's
what you are seeing here.
--
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The educated person is not the person
who can answer the questions, but the
person who can question the answers -- T. Schick Jr
Next public appearances:
March 2004 Hotsos Symposium - The Burden of Proof
March 2004 Charlotte NC OUG - CBO Tutorial
April 2004 Iceland
One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html
Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___February
____UK___June
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
"Daniel Morgan" <damorgan_at_x.washington.edu> wrote in message
news:1077300834.922938_at_yasure...
> Last night while teaching DBMS_APPLICATION_INFO I found something
> in v$sqlarea that is undocumented at tahiti.oracle.com (9.2.0.4)
>
> SQL> select distinct optimizer_mode from v$sqlarea;
>
> OPTIMIZER_MODE
> -------------------------
> CHOOSE
> MULTIPLE CHILDREN PRESENT
> NONE
>
>
> Can anyone explain what the MULTIPLE CHILDREN PRESENT optimizer
> mode is?
>
> Thanks.
>
> --
> Daniel Morgan
> http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
> http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
> damorgan_at_x.washington.edu
> (replace 'x' with a 'u' to reply)
>
Received on Fri Feb 20 2004 - 13:10:48 CST
