This content has been marked as final. Show 9 replies
The error you see is a bug/feature of MVs & FGAC.
See MetaLink Note: 158187.1
Could you please elaborate a bit about security enhancement?
In 11g, creating a materialized view on table that a policy defined on it, is possible?
The following sohuld work or it's a bug in 11g?
IF dbms_mview.i_am_a_refresh THEN
I think it doesn't apply in your case.
This was about an MV on a remote database table.
Apologies for this.
Both views do not contain any function call.
When you added the i_am_a_refresh check, was this to a static or dynamic policy?
The policy defined as dynamic.
You asked if the materialized view contained a function call.
I'm getting this error on Oracle 11gR1 and my materialized view does contain a function call to a package function.
Have you got a suggestion for this? We seem to have the mat view refresh working again, but if we drop and recreate the materialized view, we get an error on create.