||Oracle Tips by Burleson
Chapter 11 Oracle Fine Grained Auditing
true, the corresponding handler functions are
triggered. This may cause some confusion in handling the policies,
but in most cases this provides flexibility to the setup. The
individual policies can be enabled or disabled based on
requirements, without affecting the others.
All the administrative operations for policies
are done using procedures defined in the supplied package dbms_fga.
Here are the common operations.
The policies can be dropped by the following
You should be aware of a bug 2713401 that
prevents the policy from being dropped. In this bug, attempts to
drop the policy using the above statement will fail with “ORA-28102:
policy does not exist” error message. Remember, this is a bug, so it
might have been fixed in later releases. If the bug affects your
particular release, please read on in this section; otherwise,
please skip it.
In order to
correct the problem, the best approach is to call Oracle Support and
have them address the problem. In development systems, however, here
is a solution you could try. We urge you to strongly consider
against running it on production, as it is unsupported by Oracle,
but it seems to work and can be attempted in development. The
authors do not assume any
The above text is
an excerpt from:
Oracle Privacy Security Auditing
Final Word on Oracle Security
This is the only authoritative
book on Oracle Security, Oracle Privacy, and Oracle Auditing written
by two of the world’s leading Oracle Security experts.
This indispensable book is only
and has an
immediate download of working security scripts: