ORA-14299: total number of partitions/subpartitions exceeds the maximum limit

Cause : The total number of combined fragments specified in partitions /subpartitions exceeds 1048575.

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

Reissue the statement with fewer number of fragments

update : 23-04-2017

ORA-14299 - total number of partitions/subpartitions exceeds the maximum limit
ORA-14299 - total number of partitions/subpartitions exceeds the maximum limit

  • ora-40203 : model string does not exist
  • ora-30938 : No prefix defined for namespace 'string' (particle string)
  • ora-16816 : incorrect database role
  • ora-24043 : destination string uses a reserved name, names with AQ$_ prefix are not valid
  • ora-16633 : the only instance of the database cannot be removed
  • ora-25466 : data not specified for variable name: string
  • ora-01038 : cannot write database file version string with ORACLE version string
  • ora-33452 : (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled.
  • ora-36881 : (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP.
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-21700 : object does not exist or is marked for delete
  • ora-02087 : object locked by another process in same transaction
  • ora-22625 : OCIAnyData is not well-formed
  • ora-12872 : First slave parse gave different plan
  • ora-19681 : block media recovery on control file not possible
  • ora-08190 : restore point string is from a different incarnation of the database
  • ora-31112 : fail to string for string port using xdb configuration
  • ora-01665 : control file is not a standby control file
  • ora-12731 : invalid collation class in regular expression
  • ora-39726 : unsupported add/drop column operation on compressed tables
  • ora-13283 : failure to get new geometry object for conversion in place
  • ora-24124 : invalid ACTION parameter passed to DBMS_REPAIR.string procedure
  • ora-06977 : X.25 Driver: X.25 Level 2 failure
  • ora-24912 : Listener thread failed. string
  • ora-16007 : invalid backup control file checkpoint
  • ora-12449 : Labels specified for user must be of type USER
  • ora-21612 : key is already being used
  • ora-00483 : During shutdown a process abnormally terminated
  • ora-23351 : parameter datatype string for procedure string not supported
  • ora-01689 : syntax error in clause "string" of string
  • 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.