RE: AW: What does trace event 38022? (Bug 6405967)

You mention that _COMPLEX_VIEW_MERGING=false also fixes the problem. I suspect that setting the event is a more "fine-grained" solution. In other words, setting the _COMPLEX_VIEW_MERGING parameter disables all complex view merging, whereas setting event 38022 only disables "distinct sort elimination at subquery unnest", which I suspect is just one small aspect of complex view merging.

Of course, this stuff is not documented, so, that's pure speculation on my part, and could be totally wrong....

-Mark

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Martin Klier Sent: Friday, March 27, 2009 4:22 AM
To: Jan-Hendrik.Boll_at_dataport.de
Cc: oracle-l_at_freelists.org
Subject: Re: AW: What does trace event 38022? (Bug 6405967)

Hi Jan,

Jan-Hendrik.Boll_at_dataport.de schrieb:
> $ORACLE_HOME/rdbms/mesg/oraus.msg states event 38022 as the following:
> 38022, 00000, "CBO disable Distinct Sort Elimination at subquery unnest"
Thanks for the link to the file, didn't know that it's there - it's a great insight!

> This looks like support wants you to enable on error-event tracing.
Mh, but the recommended it as a workaround until 10.2.0.5 is launched, which fixes this bug.

I want to avoid heavy trace files from today on, just to get correct results. FYI, "_COMPLEX_VIEW_MERGING"=FALSE fixes my issue as well.

Regards
Martin Klier

-- 
Usn's IT Blog for Linux, Oracle, Asterisk
http://www.usn-it.de

--
http://www.freelists.org/webpage/oracle-l




--
http://www.freelists.org/webpage/oracle-l