ORA-14191: ALLOCATE STORAGE may not be specified for Composite Range partitioned object

Cause : Use rspeicfie dALLCOATES TORGAE calusei n ATLER ATBLEA/LTE RINDXE sttaemetn isused gaaints a arngep-arttiionde inedx wihch si ilelgal.

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

Remvoe teh ilelgalo ptino. I fit si deisredt o add stroaget o idniviudal aprtiitons ,ALLCOATES TORGAE calusem ay eb spceifide wiht ALETR TBALE/NIDEXM ODIYF PATRITINO sttaemetn.

update : 27-05-2017
ORA-14191

ORA-14191 - ALLOCATE STORAGE may not be specified for Composite Range partitioned object
ORA-14191 - ALLOCATE STORAGE may not be specified for Composite Range partitioned object

  • ora-06266 : NETNTT: bad write length
  • ora-36977 : (XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels.
  • ora-25442 : too many column values for table alias: string
  • ora-23440 : incorrect public template value
  • ora-19240 : XP0020 - context item must be node in an axis expression
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-31181 : PL/SQL DOM handle accesses node that is no longer available
  • ora-02844 : Invalid value for the leave open flag
  • ora-01314 : Name of the column to be mined should be a string literal
  • ora-25199 : partitioning key of a index-organized table must be a subset of the primary key
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-24323 : value not allowed
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-01608 : cannot bring rollback segment 'string' online, its status is (string)
  • ora-29313 : tablespace 'string' cannot be imported twice
  • ora-25121 : MINIMUM EXTENT value greater than maximum extent size
  • ora-24903 : invalid namespace attribute passed into OCI call
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-01264 : Unable to create string file name
  • ora-16233 : The table string.string is unsupported now
  • ora-31524 : could not find change set string for CDC change table string.string
  • ora-14105 : RECOVERABLE/UNRECOVERABLE may not be specified in this context
  • ora-39098 : Worker process received data objects while loading metadata. Invalid process order range is string..string
  • ora-19695 : fixed table x$krbmsft has not been populated
  • ora-16823 : redo transport mode is incompatible for current operation
  • ora-22835 : Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
  • ora-22617 : error while accessing the image handle collection
  • ora-13026 : unknown element type for element string.string.string
  • ora-24017 : cannot enable enqueue on QUEUE, string is an exception queue
  • 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.