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 : 22-09-2017
ORA-28139

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

  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-09314 : sltln: error translating logical name
  • ora-09941 : Version of orapasswd or installer is older than file.
  • ora-07457 : cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE
  • ora-29887 : cannot support row movement if domain index defined on table
  • ora-36958 : (XSFCAST26) The OFFSET value for cycle number cannot be greater than the cycle's PERIODICITY, which is number. You specified number.
  • ora-02151 : invalid tablespace name: string
  • ora-13429 : invalid xCoefficients or yCoefficients parameter(s)
  • ora-04089 : cannot create triggers on objects owned by SYS
  • ora-01033 : ORACLE initialization or shutdown in progress
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-30728 : maximum number of columns exceeded
  • ora-00359 : logfile group string does not exist
  • ora-16553 : the Data Guard broker process (DMON) failed to shutdown
  • ora-01865 : not a valid era
  • ora-38498 : invalid stored attribute for the index object : string
  • ora-26576 : cannot acquire SR enqueue
  • ora-13346 : the coordinates defining an arc are collinear
  • ora-25267 : didnt specify the signature for a reciever non-repudiable queue
  • ora-09317 : szprv: insufficient privileges
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-08112 : a composite partition may not be coalesced as a whole
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-02340 : invalid column specification
  • ora-13009 : the specified date string is invalid
  • ora-26506 : null global context
  • ora-33214 : (CINSERT02) The workspace object dimension is too large.
  • ora-36761 : (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property.
  • ora-14015 : too many partition descriptions
  • 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.