Why would oracle disable a fix by default?
- From: "Michael McMullen" <ganstadba@xxxxxxxxxxx>
- To: "'Oracle Discussion List'" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 11 May 2010 11:28:07 -0400
A colleague has run into this bug but we are a little suspicious that the
fix is disabled by default. Is this common?
There is another known bug (Bug 6376915) related to HW enqueue contention
for ASSM LOB segments. Although the fix is included in the 10.2.0.4
patchset, it is disabled by default and needs to be enabled with event
44951.
Other related posts:
