How To Avoid Materialized View Problem Against Needed Privileges
(Doc ID 1586366.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Cloud Infrastructure - Database Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.4 [Release 11.2]
Information in this document applies to any platform.
Reviewed 10-Jun-2014.
Goal
When Materialized Views are reported as invalid in (USER/ALL/DBA)_OBJECTS and (USER/ALL/DBA)_MVIEWS reports both the compile_state
and the staleness as 'COMPILATION_ERROR'.
Moreover, This problem cannot be solved by compiling the MView nor by refreshing the snapshot.
In this scenario, likely some granting privileges issues are causing that.
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.
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 |