Skip to Main Content
  • Questions

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

Breadcrumb

Connor and Chris will both be at AI World from October 12 to October 17 , the premier Oracle conference of 2025. If you're in Vegas, please come say Hi or pop into our sessions

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

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's channel and Chris's channel from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.

More to Explore

Data Pump

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