Skip to Main Content
  • Questions
  • How to avoid materialized views having staleness="IMPORT" after importing schema by expdp/impdp?

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Tin Ho.

Asked: February 10, 2017 - 1:41 am UTC

Last updated: February 13, 2017 - 6:04 am UTC

Version: 11.2.0.3

Viewed 1000+ times

You Asked

After importing schema by expdp/impdp, I have materialized views with staleness set to "IMPORT". That is, complete refresh is needed to fast refresh is needed later on. However, those materialized views (as star schema commonly seen in datamart) take me 2 days or more to complete refresh. It is something I wish to avoid.

So my question is, whether it is possible avoid materialized views having staleness set to "IMPORT" after schema is imported by expdp/impdp tool?

and Connor said...

There isnt, but perhaps you could try an alternative means

1) export the schema WITHOUT the mviews

2) import into the target. So we have everythng *except* the mviews

3) on the target, do: create table MVIEW_NAME as select * from MVIEW_NAME@source

4) create materialized view MVIEW_NAME using the 'on prebuilt table' clause


Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Tin Ho Mak, February 24, 2017 - 1:29 am UTC


More to Explore

Data Pump

All of the database utilities including Data Pump are explained in the Utilities guide.