ORA-942 on Materialized View Refresh after Master Mview Recreated on Different Table
(Doc ID 867042.1)
Last updated on NOVEMBER 03, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 22.214.171.124 [Release 10.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Problem with a Nested Materialized View refresh.
-- Problem Statement:
ORA-942 during mview refresh process.
There is an mview based on another mview. We changed base table on master mview, so this parent mview
points to a new master table.
Dropping and recreating the child mview that reports ORA-942 fixes the issue.
The table on which the master mview was based was changed to a table with a different definition.
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