How to Perform an EXPDP/IMPDP for a SCHEMA with a MATERIALIZED VIEW. Highlighting the IMPORT Staleness and UNKNOWN_IMPORT column in DBA_MVIEWS
(Doc ID 1579866.1)
Last updated on MARCH 10, 2023
Applies to:
Oracle Database Backup Service - Version N/A and laterOracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 9.2.0.8 and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Goal
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample or bulit-in schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
This document will cover a COMPLETE Refresh only MVIEW. It also should be noted that the only side affect here is with the Optimizer and how this approaches
Query Rewrite. The data in the mview is not affected, other than the fact the Optimizer has no idea how current this is, which is why it has a Status of IMPORT.
Once a COMPLETE Refresh is performed on this mview then all status's go back to FRESH, as per a normal COMPLETE Refresh.
Creating the Materialized View and Schema.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |