RE: Why would oracle disable a fix by default?
- From: "Mark W. Farnham" <mwf@xxxxxxxx>
- To: <ganstadba@xxxxxxxxxxx>, "'Oracle Discussion List'" <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 11 May 2010 12:01:11 -0400
Usually (beware averages over 25 year time frames) that means a fix has less
than the usual regression testing so there is more possibility that it
screws up something else. So you set the event to cure a known problem at
your site, Oracle gets the patchset out in a more timely fashion, and if
they discover a problem unsetting the event cures that and at least you're
no worse than before.
mwf
_____
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Michael McMullen
Sent: Tuesday, May 11, 2010 11:28 AM
To: 'Oracle Discussion List'
Subject: Why would oracle disable a fix by default?
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:
