Dependent Objects Gets Invalidated When Policy Is Added Or Dropped
(Doc ID 1090749.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.5 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
If applying the VPD policy on a synonym (or deleting it, possibly other operations trigger the same problem), the plsql depending on the same synonyms on the base table is invalidated.
This does not occur when the VPD policy is applied directly on the base table.
The problem tends to become even more complex when the dependency chain is deep. Otherwise, it is benign and hardly noticeable.
This can be experimented as below:
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