Re: Why alter table move can repair the problem awr not generated ?
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: luolee.me@xxxxxxxxx
- Date: Mon, 6 Jan 2014 06:41:07 +0000
We'll need the error encountered by the AWR snapshot job to determine a
suitable answer. (which may of course be that it was a coincidence). You
can find this (if my memory is good) in dba_scheduler_job_run_details.
On Jan 6, 2014 1:59 AM, "LuoLee.me" <luolee.me@xxxxxxxxx> wrote:
> Dear list,
> I meet a problem that awr snapshot didn't generate correctly last
> week. I attempt to truncate the table sys.WRI$_OPTSTAT_HISTHEAD_HISTORY,
> but it didn't take effect.
> The other way, I use the "alter table
> sys.WRI$_OPTSTAT_HISTHEAD_HISTORY move" in restricted mode, it
> became effect. I know the way that truncate the table could do it
> sometimes, but this time, it fails.
>
> We all know that "alter table move" could lower the highest watermark,
> but why it can repair the awr not generated problem, and why truncate could
> not here.
> Anyone know the truth ?
> Thanks in advance.
>
Other related posts:
