ORA-1031 Creating an On Commit Materialized View on Another Schema
(Doc ID 433860.1)
Last updated on NOVEMBER 07, 2023
Applies to:
Oracle Cloud Infrastructure - Database Service - Version N/A and laterOracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
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.
In a secure environment with a restricted access to schemas and privileges, where:
Base tables are owned by schema A.
Materialized views must be owned by schema B.
An external group is accessing with the schema C.
If schema C needs to create a local on commit materialized view under schema B, which references tables on schema A, the create materialized view may fail with error ORA-1031 (insufficient privileges).
Executing as C:
This statement does not fail if the create materialized view is executed as user B.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |