Re: Refresh Materialized view manually
From: ddf <oratune_at_msn.com>
Date: Wed, 3 Jun 2009 08:34:27 -0700 (PDT)
Message-ID: <beeaad9c-37a3-4ca0-85de-56cf131e58f3_at_q14g2000vbn.googlegroups.com>
On Jun 3, 3:53 am, Randolf Geist <mah..._at_web.de> wrote:
> > We refresh this view every 30 seconds automatically.
> > Sometimes underlying tables will be updated by users and they want to
> > generate a report right away with the updated data.
> > They don't want to wait next 30 seconds, for the latest data. So want
> > to provide a manually refresh so that latest data will updated in
> > materialized view.
>
> Naga,
>
> although I second the doubts that this design is sound, if you really
> have the need for "real-time" refreshes why not go for the ON COMMIT
> refresh clause of the materialized view?
>
> Regards,
> Randolf
>
> Oracle related stuff blog:http://oracle-randolf.blogspot.com/
>
> SQLTools++ for Oracle (Open source Oracle GUI for Windows):http://www.sqltools-plusplus.org:7676/http://sourceforge.net/projects/sqlt-pp/
Date: Wed, 3 Jun 2009 08:34:27 -0700 (PDT)
Message-ID: <beeaad9c-37a3-4ca0-85de-56cf131e58f3_at_q14g2000vbn.googlegroups.com>
On Jun 3, 3:53 am, Randolf Geist <mah..._at_web.de> wrote:
> > We refresh this view every 30 seconds automatically.
> > Sometimes underlying tables will be updated by users and they want to
> > generate a report right away with the updated data.
> > They don't want to wait next 30 seconds, for the latest data. So want
> > to provide a manually refresh so that latest data will updated in
> > materialized view.
>
> Naga,
>
> although I second the doubts that this design is sound, if you really
> have the need for "real-time" refreshes why not go for the ON COMMIT
> refresh clause of the materialized view?
>
> Regards,
> Randolf
>
> Oracle related stuff blog:http://oracle-randolf.blogspot.com/
>
> SQLTools++ for Oracle (Open source Oracle GUI for Windows):http://www.sqltools-plusplus.org:7676/http://sourceforge.net/projects/sqlt-pp/
Depending upon how long the refresh actually takes, using the ON COMMIT refresh option can increase the time required to complete the insert/update/delete transactions to the defining tables, which may be an unacceptable option especially if this is an OLTP system. Granted a 30-second refresh schedule is (in my mind) ridiculous, but using ON COMMIT may slow down transactions to an unacceptable level.
Of course we know nothing of this system outside of the 30-second refresh schedule for a materialized view for which we have no definition.
David Fitzjarrell Received on Wed Jun 03 2009 - 10:34:27 CDT