ORA-28139: Maximum allowed Fine Grain Audit Policies Exceeded

Cause : A maximum of 256 policies can be enabled on an object

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Drop or disable an existing policy before creating more

update : 25-04-2017
ORA-28139

ORA-28139 - Maximum allowed Fine Grain Audit Policies Exceeded
ORA-28139 - Maximum allowed Fine Grain Audit Policies Exceeded

  • ora-38439 : invalid operation "string"
  • ora-32637 : Self cyclic rule in sequential order MODEL
  • ora-16619 : health check timed out
  • ora-16518 : unable to allocate virtual instance id
  • ora-00394 : online log reused while attempting to archive it
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-01519 : error while processing file 'string' near line string
  • ora-08318 : sllfsk: Error reading file
  • ora-02454 : Number of hash keys per block (string) exceeds maximum of string
  • ora-19590 : conversation already active
  • ora-16576 : failed to update Data Guard configuration file
  • ora-01078 : failure in processing system parameters
  • ora-03214 : File Size specified is smaller than minimum required
  • ora-07416 : slpath: pathname construction failed; lack of output buffer space.
  • ora-30334 : illegal dimension level name
  • ora-18009 : one or more outline system tables do not exist
  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-02479 : error while translating file name for parallel load
  • ora-39084 : cannot detach job string for user string
  • ora-14318 : DEFAULT partition must be last partition specified
  • ora-36646 : (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension.
  • ora-37074 : (XSMCSESS02) Variable workspace object has no default aggmap.
  • ora-26095 : unprocessed stream data exists
  • ora-01901 : ROLLBACK keyword expected
  • ora-12994 : drop column option only allowed once in statement
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • ora-03202 : the scan limit specification is invalid
  • ora-02285 : duplicate START WITH specifications
  • ora-29319 : datafile string is not correct
  • ora-10618 : Operation not allowed on this segment
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.