Does a Materialized View have to be Recreated when the Master is Moved to New Tablespace?
(Doc ID 1306955.1)
Last updated on SEPTEMBER 29, 2021
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Express Cloud 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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
There is a table in the master database. It has a MV log defined "WITH PRIMARY KEY EXCLUDING NEW VALUES" option. There is an MView defined on this table in another database.
The master table is huge and causing some performance issues so, it will be reorganized. The plan is to move this table to a new tablespace and then rebuild all the indexes.
Is it required to rebuild or complete refresh the MView when this table is reorganized in the master site?
Cause
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
| Symptoms |
| Cause |
| Solution |