RE: AW: What does trace event 38022? (Bug 6405967)
- From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxx>
- To: "usn@xxxxxxxxx" <usn@xxxxxxxxx>, "Jan-Hendrik.Boll@xxxxxxxxxxx" <Jan-Hendrik.Boll@xxxxxxxxxxx>
- Date: Fri, 27 Mar 2009 12:54:20 -0400
Hi Martin,
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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Martin Klier
Sent: Friday, March 27, 2009 4:22 AM
To: Jan-Hendrik.Boll@xxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: AW: What does trace event 38022? (Bug 6405967)
Hi Jan,
Jan-Hendrik.Boll@xxxxxxxxxxx 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
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
