ORA-32636: Too many rules in MODEL

Cause : The number of rules (possibly after rule unfolding) exceeded the maximum number of rules allowed.

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

Reduce the number of rules.

update : 16-08-2017
ORA-32636

ORA-32636 - Too many rules in MODEL
ORA-32636 - Too many rules in MODEL

  • ora-39084 : cannot detach job string for user string
  • ora-13284 : failure to copy geometry object for conversion in place
  • ora-24025 : invalid value string, QUEUE_PAYLOAD_TYPE should be RAW or an object type
  • ora-13707 : Either the start snapshot string or the end snapshot string is incomplete or missing key statistics.
  • ora-32013 : failure in verifying parameters from the restored SPFILE
  • ora-27301 : OS failure message: string
  • ora-19851 : OS error while managing auxiliary database string
  • ora-12855 : cannot run parallel or insert direct load in a loopback
  • ora-19906 : recovery target incarnation changed during recovery
  • ora-19651 : cannot apply offline-range record to datafile string: SCN mismatch
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-28264 : Client identifier is too long
  • ora-19960 : Internal use only
  • ora-13784 : cannot accept SQL profiles for all statements in the "SQL Tuning Set"
  • ora-19585 : premature end of volume on piece string
  • ora-31901 : the current operation was cancelled by the user
  • ora-26078 : file "string" is not part of database being loaded
  • ora-29703 : error occurred in global enqueue service operation
  • ora-38484 : FUNCTION/PACKAGE/TYPE string does not exist
  • ora-22909 : exceeded maximum VARRAY limit
  • ora-02258 : duplicate or conflicting NULL and/or NOT NULL specifications
  • ora-00382 : %s not a valid block size, valid range [string..string]
  • ora-15112 : No diskgroups are currently mounted.
  • ora-06791 : TLI Driver: poll returned error event
  • ora-26747 : The one-to-many transformation function string encountered the following error: string
  • ora-29285 : file write error
  • ora-29911 : null scan context returned by ODCIIndexStart() routine
  • ora-23475 : key column string must be sent and compared
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-03001 : unimplemented feature
  • 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.