Re: Why would oracle disable a fix by default?
- From: Jared Still <jkstill@xxxxxxxxx>
- To: ganstadba@xxxxxxxxxxx
- Date: Tue, 11 May 2010 14:59:16 -0700
On Tue, May 11, 2010 at 8:28 AM, Michael McMullen <ganstadba@xxxxxxxxxxx>wrote:
> A colleague has run into this bug but we are a little suspicious that the
> fix is disabled by default. Is this common?
>
>
>
It's common in the SAP world.
Here's an example for SAP Netweaver (7.something?) on Oracle 10.2.0.4 on
Windows.
alter system set event=
"10027 trace name context forever, level 1",
"10028 trace name context forever, level 1",
"10162 trace name context forever, level 1",
"10183 trace name context forever, level 1",
"10191 trace name context forever, level 1",
"10411 trace name context forever, level 1",
"10629 trace name context forever, level 32",
"10891 trace name context forever, level 1",
"14532 trace name context forever, level 1",
"38068 trace name context forever, level 100",
"38087 trace name context forever, level 1",
'600 trace name errorstack level 3, systemstate level 10' ,
'600 trace name errorstack level 3',
'600 trace name systemstate level 10',
'7445 trace name errorstack level 3',
"10142 trace name context forever, level 1",
"38085 trace name context forever, level 1",
"44951 trace name context forever, level 1024"
scope=spfile;
alter system set "_sort_elimination_cost_ratio" = 10 scope=both;
alter system set "_fix_control"=
'5705630:ON',
'5765456:3' ,
"6221403:ON",
"6329318:ON",
"6430500:ON",
"6440977:ON",
"6626018:ON",
"6670551:ON",
"6972291:ON",
"7325597:ON"
scope=both;
alter system set optimizer_dynamic_sampling=2 scope=both;
alter system set "_optimizer_mjc_enabled"=false scope=both;
alter system set "_optim_peek_user_binds"=false scope=both;
alter system set "_optimizer_better_inlist_costing"=off scope=both;
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
Other related posts:
