Materialized View Triggers, Constraints (ORA-00001), and Longs
(Doc ID 67424.1)
Last updated on SEPTEMBER 08, 2021
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle 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.
This document covers information regarding the interaction between materialized views (mviews) and triggers, unique indexes, primary keys, declarative / referential integrity constraints, and long data types. This article describes why Oracle imposes restrictions on these and how to get around them, if possible.
Oracle7 and Oracle8 server releases imposed many restrictions on materialized views; some of these restrictions have been removed with Oracle 8i, 9i, and on up through 12c. This note applies to those that persist among all the versions.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!