Re: Mviews Refresh Timings
From: ddf <oratune_at_msn.com>
Date: Mon, 9 Mar 2009 08:15:35 -0700 (PDT)
Message-ID: <6026203b-2d82-4f16-9326-42fd5bb53693_at_s28g2000vbp.googlegroups.com>
On Mar 9, 8:47 am, "lyx..._at_gmail.com" <lyx..._at_gmail.com> wrote:
> Thanks David for suggestion,
>
> What I am thinking to create one trigger on system level on "Truncate"
> specifically if segment is one of these
> Mview. I can just create this trigger before starting this job.
>
> As per my knowledge whenever we do complete refresh, Oracle first
> truncate the base mview and then will insert
> data into this.
>
> So - trigger will help when truncate happened and later on I can track
> dba_mview,refresh_Time when it was completed.
>
> Do you see this approach feasible/possible. ?
>
> Regards,
Date: Mon, 9 Mar 2009 08:15:35 -0700 (PDT)
Message-ID: <6026203b-2d82-4f16-9326-42fd5bb53693_at_s28g2000vbp.googlegroups.com>
On Mar 9, 8:47 am, "lyx..._at_gmail.com" <lyx..._at_gmail.com> wrote:
> Thanks David for suggestion,
>
> What I am thinking to create one trigger on system level on "Truncate"
> specifically if segment is one of these
> Mview. I can just create this trigger before starting this job.
>
> As per my knowledge whenever we do complete refresh, Oracle first
> truncate the base mview and then will insert
> data into this.
>
> So - trigger will help when truncate happened and later on I can track
> dba_mview,refresh_Time when it was completed.
>
> Do you see this approach feasible/possible. ?
>
> Regards,
It sounds like a workable plan, as long as you manage the table where you'll be storing this data. Remember that if the trigger fails the refresh will fail.
David Fitzjarrell Received on Mon Mar 09 2009 - 10:15:35 CDT