Moving OPTSTAT objects from SYSAUX
- From: Wittenmyer Joel - CO <WITTENMYERJ@xxxxxxxx>
- To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
- Date: Sun, 4 Jun 2006 09:07:35 -0500
We encountered bug 4288876 in 10.2.0.1.0 and applied the one-off patch,
which failed to have any effect on the bug at all. Apparently this is not
uncommon with this bug / patch. The next step is to apply patchset
10.2.0.2, which apparently succeeds even where the one-off patch fails. I'm
always loathe to: 1) install / use version 1 of anything Oracle; 2) apply
the latest patchset. In our architecture I was able to isolate the bug
behaviour to the statistics gathering processes doing DML on the OPTSTAT
objects in the SYSAUX tablespace. I therefore tested moving the OPTSTAT
objects out of SYSAUX, exercising the statistics gathering processes, moving
the objects back into SYSAUX, and again exercising the processes.
Everything seems to be fine. However, I read a note in "10g Insider
Solutions" that states that these particular objects CANNOT be moved from
SYSAUX.
Finally, the questions:
Has anyone had experiences one way or the other moving these objects out of
SYSAUX?
Does anyone know why it would be a bad idea to do so?
Thanks in advance,
Joel Wittenmyer
Other related posts:
