My Oracle Support Banner

Ws:Permission Issues When Using Refresh Fast On Commit And Materialized View Log (Doc ID 418726.1)

Last updated on OCTOBER 04, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


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.

-- Problem Statement:
Attempting to create a MView to replicate data from one schema to another. Looking to use fast
refresh so that only the changed rows are populated on commit (rather than full refresh).IT looks like there are permission problems. But,not using roles.

By granting DBA to <Testschema2>,able to create MView, But when issue an insert to <Testschema1>, getting ORA-12008: error in materialized view refresh path -
ORA-00942: table or view does not exist. If don't grant <Testschema2> DBA privs, then getting
ORA-12018: following error encountered during code generation for "<Testschema2>"."<TEST_TABLE>" -ORA-00942:
table or view does not exist.
Also insuffecent privilege error may occur.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.