This content has been marked as final. Show 4 replies
or fast refreshes of a materialized view.1 person found this helpful
Thanks very much,Andy.
This is very helpful.
I wonder if I should create all columns on the MV Log in the source or have this setting as default?
And just to confirm that FAST refresh does not need the UPDATE switch at MV creation, is this correct ( as only single direction update is needed ) ?
Lastly, I presume if did an impdp / imp into Database B from Database A ( only the table in discussion ), i just need to redo the same procedure once ?
thanks so much.
No problem Clement.If there is a primary key on the table that will be sufficient for the materialized view log, otherwise you can use rowid:
And, no, you don't need UPDATE on creation. It sounds like you only need "one-way direction" so the default READ ONLY should be sufficient for your needs. You lost me on the impdp/imp question. There is no need to exp/imp, the CREATE MATERIALIZED VIEW is going to do all of the initial heavy lifting. Depending on how you create it you can schedule the fast refresh interval with NEXT (every five minutes for example):
See for more details/examples:
CREATE MATERIALIZED VIEW catalog REFRESH FAST START WITH SYSDATE NEXT SYSDATE + 5/24/60 WITH PRIMARY KEY AS SELECT * FROM product_information@orcl1;
And welcome to the forums!
That's a concise an answer! the impdp part was my assumption that the table(source) might be overwritten (impdp) in case of data recovery issues in the source ( modified). Cheers mate.