Re: MV logs with Oracle's auto extent control
- From: "Thomas Day" <tomdaytwo@xxxxxxxxx>
- To: "Hemant K Chitale" <hkchital@xxxxxxxxxxxxxx>
- Date: Fri, 5 Oct 2007 12:59:35 -0400
On 10/5/07, Hemant K Chitale <hkchital@xxxxxxxxxxxxxx> wrote:
>
>
> A Truncate doesn't actually do a "drop and recreate". It drops all
> extents *after* the first one.
> Apparently, your first extent for those MVLog Tables has been
> 8MB. Why ? Not sure yet.
> But here's a suggestion. Try dropping and recreating the MV logs.
> (DROP SNAPSHOT LOG ON TABLE <tablename> ; followed by the CREATE
> SNAPSHOT LOG ... )
Yes, that will work; however, we're doing the refresh once an hour. We have
a lot of mv logs. I'd prefer to keep them in place if I can.
- References:
- MV logs with Oracle's auto extent control
- From: Thomas Day
- Re: MV logs with Oracle's auto extent control
- From: Hemant K Chitale
Other related posts:
- » MV logs with Oracle's auto extent control
- » Re: MV logs with Oracle's auto extent control
- » Re: MV logs with Oracle's auto extent control
- MV logs with Oracle's auto extent control
- From: Thomas Day
- Re: MV logs with Oracle's auto extent control
- From: Hemant K Chitale