How to Solve :
Oracle database error code ORA-30372 – fine grain access policy conflicts with materialized view
Oracle Database Error Code ORA-30372 Description :
fine grain access policy conflicts with materialized view
Error Cause:
A fine grain access control procedure has applied a non-null policy to the query for the materialized view.
How to Solve :
In order for the materialized view to work correctly, any fine grain access control procedure in effect for the query must return a null policy when the materialized view is being created or refreshed. This may be done by ensuring that the usernames for the creator, owner, and invoker of refresh procedures for the materialized view all receive a null policy by the user-written fine grain access control procedures.
Filed under: How to Solve, Oracle 10g, Oracle 11g, Oracle 9i, Oracle Error Codes Etiketler: ora - 30372, 30372, about oracle ORA-30372 error, fine grain access policy conflicts with materialized view, help ORA-30372 about, ORA-30372 error code, ORA-30372 problem, Oracle 9i 10g 11g, Oracle Database Server Error Messages, Oracle Error Codes, oracle number 30372 error code, oracle ORA-30372 example
No Comment Yet
No Comment Yet
Recent Entries
- Oracle database error code ORA-29959 – error in the execution of the string routine for one or more of the index partitions
- Oracle database error code ORA-31601 – Function string cannot be called now that fetch has begun.
- Oracle database error code ORA-29958 – fatal error occurred in the execution of ODCIINDEXCREATE routine
- Oracle database error code ORA-31600 – invalid input value string for parameter string in function string
- Oracle database error code ORA-29957 – cannot create a function-based domain index on a string table
- Oracle database error code ORA-31604 – invalid string parameter “string” for object type string in function string
- Oracle database error code ORA-29961 – too many warnings occurred in the execution of ODCIIndex DDL routine
Search Oracle Error Codes and Descriptions:
Be The First To Comment
Similar Errors
Please Leave Your Comments Below