How to Handle Materialized Views When You Upgrade or Clone a Database
(Doc ID 1406586.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and later Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Database Backup Service - Version N/A and later Information in this document applies to any platform.
Goal
There are several ways by which to upgrade or clone a database. For example, (1) the Database Upgrade Assistant (DBUA), (2) RMAN clone to auxiliary database, (3) copying files from a cold/hot backup, (4) export/import, or (5) export/import with transportable tablespaces (TTS). Your materialized views should still be fast refreshable after one of these operations, provided you follow the actions given below for your particular case.
This note is applicable only to read-only materialized views; updatable materialized views are not covered here.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
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!
