Re: Fast Refresh Materialized View on Prebuilt Table

Is there a specific reason you wish to copy the table from source to target manually and then create the mview using prebuilt?

We use mview replication quite a bit, and I've always just created the fast refreshable mviews with "build immediate" and that way let the mview do the initial copying of the table.
That way the source mview log keeps the changes during the mview build and then the first fast refresh afterwards will get those changes.

Regards

Kim Berg Hansen

http://dspsd.blogspot.com
kibeha_at_gmail.com
_at_kibeha

On Mon, Oct 6, 2014 at 12:25 PM, Charlotte Hammond < dmarc-noreply_at_freelists.org> wrote:

> Hi All,
>
> I'm creating a large fast-refreshable materialized view using a prebuilt
> table.
>
> The problem I have is that by the time I have copied the table from the
> source system to the target system several hours have passed and there are
> now numerous changes on the target. As soon as I issue the CREATE
> MATERIALIZED VIEW command the log is deleted and the fast refresh starts on
> a table which is by now out of date.
>
> I'm looking for a good way to sync up the changes made during the copy
> period. I've got some ideas using triggers (and possibly a small outage
> on the source) but it's seems messy. I'm wondering if I'm missing some
> clean / built-in functionality to resolve this?
>
> The database is 11.2.0.4 SE
>
> Thanks in advance for any ideas!
> Charlotte
>

--
http://www.freelists.org/webpage/oracle-l